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.

Sign up for GitHub

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

Jump to bottom

Make it clear that normative requirements on CONNECT are only for HTTP/1.1 #2941

Open
bemasc opened this issue Nov 7, 2024 · 0 comments · May be fixed by #2944
Open

Make it clear that normative requirements on CONNECT are only for HTTP/1.1 #2941

bemasc opened this issue Nov 7, 2024 · 0 comments · May be fixed by #2944
Labels
optimistic-upgrade draft-ietf-httpbis-optimistic-upgrade

Comments

@bemasc
Copy link
Contributor

bemasc commented Nov 7, 2024

The current text could be interpreted as applying to other HTTP versions, which is not the intent.

cc @tfpauly
@bemasc bemasc added the optimistic-upgrade draft-ietf-httpbis-optimistic-upgrade label Nov 7, 2024
@bemasc bemasc changed the title Make it clear that normative requirements on CONNECT or only for HTTP/1.1 Make it clear that normative requirements on CONNECT are only for HTTP/1.1 Nov 7, 2024
bemasc added a commit that referenced this issue Nov 8, 2024
@bemasc
[optimistic-upgrade] Clearly limit recommendations to HTTP/1.1
92c4f0a 
Fixes #2941
@bemasc bemasc linked a pull request Nov 8, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
optimistic-upgrade draft-ietf-httpbis-optimistic-upgrade
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[optimistic-upgrade] Clearly limit recommendations to HTTP/1.1 httpwg/http-extensions
1 participant
@bemasc