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

CONNECT, OPTIONS and request-target #340

Closed
mnot opened this issue Mar 20, 2020 · 0 comments · Fixed by #352
Closed

CONNECT, OPTIONS and request-target #340

mnot opened this issue Mar 20, 2020 · 0 comments · Fixed by #352
Assignees
@mnot
Labels
has-proposal semantics

Comments

@mnot
Copy link
Member

mnot commented Mar 20, 2020

As discussed in #259, CONNECT and OPTIONS both have special request-target forms. This needs to be untangled so the terminology is not specific to H1.
@mnot mnot added the semantics label Mar 20, 2020
@mnot mnot mentioned this issue Mar 20, 2020
Merged
@mnot mnot self-assigned this Mar 20, 2020
@mnot mnot mentioned this issue Mar 20, 2020
Closed
mnot added a commit that referenced this issue Mar 22, 2020
@mnot
add request-target back for now
f7c4a45 
... until resolution of #340
mnot added a commit that referenced this issue Mar 23, 2020
@mnot
Define CONNECT and OPTIONS in term of target URIs
9e45e7c 
Fixes #340
@mnot mnot mentioned this issue Mar 23, 2020
Merged
This was referenced Mar 23, 2020
Closed
Closed
@mnot mnot mentioned this issue Apr 27, 2020
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mnot mnot

Labels
has-proposal semantics
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Define CONNECT and OPTIONS in term of target URIs httpwg/http-core
1 participant
@mnot