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

:path ought to be HTTP's absolute-path, not RFC3986's path-absolute #906

Closed
wtarreau opened this issue Aug 19, 2021 · 0 comments · Fixed by #910
Closed

:path ought to be HTTP's absolute-path, not RFC3986's path-absolute #906

wtarreau opened this issue Aug 19, 2021 · 0 comments · Fixed by #910

Comments

@wtarreau
Copy link
Contributor

There is currently an incompatibility between HTTP/1 and HTTP semantics definition of absolute-path and H2's use of RFC3986's path-absolute, which prevents paths from starting with //. I described it there but can paste it here if required for ease ofreading:

https://lists.w3.org/Archives/Public/ietf-http-wg/2021JulSep/0245.html

My feeling is that it was an unintentional mistake introduced between http2 drafts 4 and 5 given that it breaks sites and doesn't even look respected by H2 agents (i.e. curl, apache, varnish, firefox happily process // in h2).

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

Successfully merging a pull request may close this issue.

2 participants