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

Placement of TE: field #328

Closed
MikeBishop opened this issue Mar 11, 2020 · 2 comments
Closed

Placement of TE: field #328

MikeBishop opened this issue Mar 11, 2020 · 2 comments

Comments

@MikeBishop
Copy link
Contributor

TE: is currently defined in the HTTP/1.1 encoding. However, the definition is used by HTTP/2 and HTTP/3 to say that it MAY be present, but MUST NOT have any value other than trailers. It's a little strange, since this is definitely an artifact of wire encoding, but is used quasi-consistently across HTTP encodings.

Does this belong in Semantics?
@royfielding
Copy link
Member

I think it does. In fact, I've been thinking of moving all of the header fields to Semantics for their definition (not necessarily their associated requirements) and simply noting when a field is not allowed (or translated) in h2, etc.

@mnot
Copy link
Member

mnot commented Mar 20, 2020

Dup of #18, so closing.

@mnot mnot closed this as completed Mar 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mnot @royfielding @MikeBishop