Skip to content
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

Inaccuracy in reasoning for using headers as API key transport as opposed to query string #12

Open
ndavison opened this issue Dec 8, 2019 · 0 comments

Comments

@ndavison
Copy link

ndavison commented Dec 8, 2019

Hi there, the standards mention this:

API keys MUST NOT be included in the URL or query string. API keys MUST be included in the HTTP header (as query strings are not encrypted by TLS - headers are.)

While it's probably not a bad idea given web server logs often do keep records of a request's query string, this is not correct, as TLS happens at the transport layer and will encrypt everything in a HTTP request (method, query string, request URI, headers, body).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant