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

Reword guidance around URI generation #2902

Merged
merged 2 commits into from
Oct 8, 2024
Merged

Reword guidance around URI generation #2902

merged 2 commits into from
Oct 8, 2024

Conversation

MikeBishop
Copy link
Contributor

Mostly editorial, but touches normative text. Fixes #2853.

Copy link
Contributor

@martinthomson martinthomson left a comment

Choose a reason for hiding this comment

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

This is all so conditional that I wonder whether it even needs a SHOULD (NOT). Would it be enough to say instead.

A server can avoid this risk by constructing resource URIs
(for use in Location or Content-Location)
that do not include sensitive information.

The other options are fine.

draft-ietf-httpbis-safe-method-w-body.xml Outdated Show resolved Hide resolved
draft-ietf-httpbis-safe-method-w-body.xml Outdated Show resolved Hide resolved
Co-authored-by: Martin Thomson <mt@lowentropy.net>
@MikeBishop MikeBishop merged commit 15110ec into main Oct 8, 2024
2 checks passed
@MikeBishop MikeBishop deleted the query/how_sensitive branch October 8, 2024 15:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

Sensitive information in QUERY URLs
4 participants