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

Trailers header field doesn't need to be hop-by-hop #793

Closed
royfielding opened this issue Mar 4, 2021 · 0 comments · Fixed by #810
Closed

Trailers header field doesn't need to be hop-by-hop #793

royfielding opened this issue Mar 4, 2021 · 0 comments · Fixed by #810

Comments

@royfielding
Copy link
Member

I added "Remove Trailer from existing header fields" for the dechunking algorithm in RFC7230, and at some point we added Trailers to the list of fields to be removed hop-by-hop even when not present in Connection. However, now that preserving trailer fields is optional and separate from header fields, it makes more sense to retain Trailers as a sort of tombstone that indicates "something might be in the trailers" or "something might have been in the trailers but we lost it along the way".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

2 participants