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

Section 7.7 #930

Closed
Tracked by #914
royfielding opened this issue Aug 5, 2021 · 2 comments
Closed
Tracked by #914

Section 7.7 #930

royfielding opened this issue Aug 5, 2021 · 2 comments

Comments

@royfielding
Copy link
Member

royfielding commented Aug 5, 2021

In semantics 7.7:

A proxy MUST NOT modify the "absolute-path" and "query" parts of the received target URI when forwarding it to the next inbound server, except as noted above to replace an empty path with "/" or "*".

I found where (in the discussion of normalization in §4.2.3) we say to
replace the empty path with "/" for non-OPTIONS requests. I couldn't
find anywhere "above" where it was noted to replace an empty path with
"*" (presumably, for the OPTIONS requests), though.

@royfielding
Copy link
Member Author

This is a reference to text that was moved to HTTP/1.1 because it is version specific. I suggest we replace it with

A proxy MUST NOT modify the "absolute-path" and "query" parts of the received target URI when forwarding it to the next inbound server except as required by that forwarding protocol. For example, a proxy forwarding a request to an origin server via HTTP/1.1 will replace an empty path with "/" (Section 3.2.1 of [HTTP/1.1]) or "*" (Section 3.2.4 of [HTTP/1.1]), depending on the request method.

@mnot
Copy link
Member

mnot commented Aug 5, 2021

LGTM

royfielding added a commit that referenced this issue Aug 5, 2021
properly refer to text that has moved to [HTTP/1.1] (closes #930)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants