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

Transfer-Encoding and HTTP/1.1 "or later" #297

Closed
mnot opened this issue Feb 3, 2020 · 1 comment · Fixed by #374
Closed

Transfer-Encoding and HTTP/1.1 "or later" #297

mnot opened this issue Feb 3, 2020 · 1 comment · Fixed by #374
Assignees
@mnot
Labels
h1-messaging has-proposal

Comments

@mnot
Copy link
Member

mnot commented Feb 3, 2020 •
edited 

   A client &MUST-NOT; send a request containing Transfer-Encoding unless it
   knows the server will handle HTTP/1.1 (or later) requests; such knowledge
   might be in the form of specific user configuration or by remembering the
   version of a prior received response.
   A server &MUST-NOT; send a response containing Transfer-Encoding unless
   the corresponding request indicates HTTP/1.1 (or later).

These "(or laters)" don't seem to be accurate.
@mnot
Copy link
Member Author

mnot commented Feb 4, 2020

Suggest "(or later minor revisions of HTTP/1)"

@mnot mnot assigned mnot and unassigned royfielding May 25, 2020
mnot added a commit that referenced this issue May 25, 2020
@mnot
Don't claim Transfer-Encoding is in HTTP/2.
57cbf67 
Fixes #297.
@mnot mnot mentioned this issue May 25, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mnot mnot

Labels
h1-messaging has-proposal
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Don't claim Transfer-Encoding is in HTTP/2. httpwg/http-core
2 participants
@mnot @royfielding