-
Notifications
You must be signed in to change notification settings - Fork 149
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
query: mention security aspects of moving query component into body #1895
Comments
The security advantage mentioned here could also be viewed as a debug/development drawback because the server most of the time logs urls to have some insights on what was requested by the 'client'. |
Related to the discussion in #1909. I agree with @candoumbe that if any advice is given, some pros and cons of both alternatives should probably be enumerated. |
Security frequently comes with a lack convenience; here not having the query logged is part of why we are doing this. That said, if you want to propose text, please go ahead. |
Just my .02 - I'd be wary of making claims about security that are based just on implementation practice (e.g., what logs expose and don't). |
Ok, let's close this. |
I'm curious; we already merged #2259 which contains this text. Is that okay, or do we want a separate issue to remove that text? |
Good point. Did we forget to close the issue? |
David Slik (https://lists.w3.org/Archives/Public/ietf-http-wg/2022JanMar/0081.html):
The text was updated successfully, but these errors were encountered: