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

Explain why GET-based queries might transmit sensitive data, suggest … #441

Merged
merged 8 commits into from
Aug 27, 2020

Conversation

royfielding
Copy link
Member

…POST, link to security consideration, and provide some workarounds

Fixes #277

…POST, link to security consideration, and provide some workarounds
Copy link
Contributor

@reschke reschke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What you say about POST is true not because of the definition of POST, but because of the way HTML forms work. Maybe we should say this to avoid confusion about POST - for instance, POST can use constructed URIs as well; it's just not common.

draft-ietf-httpbis-semantics-latest.xml Outdated Show resolved Hide resolved
draft-ietf-httpbis-semantics-latest.xml Outdated Show resolved Hide resolved
@royfielding royfielding merged commit d816c84 into master Aug 27, 2020
@royfielding royfielding deleted the fielding-i277 branch August 27, 2020 06:32
triple-underscore added a commit to triple-underscore/triple-underscore.github.io that referenced this pull request Aug 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Clarification of GET versus POST for information retrieval
3 participants