Conversation
jean-michelet
approved these changes
Sep 22, 2026
| } | ||
|
|
||
| const te = reply.getHeader('te') | ||
| if (te !== undefined && !isValidHttp2Te(te)) { |
Member
There was a problem hiding this comment.
Why TE is not removed from HTTP/2 responses as well?
gurgunday
approved these changes
Sep 22, 2026
Member
|
Isn't this a breaking change? |
Member
|
I would consider this a bug fix rather than a breaking change. HTTP/2-invalid headers are removed, and users relying on invalid trailers should fix their code. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Remove connection-specific headers forbidden by HTTP/2 before Fastify writes managed responses, including Web Response and stream paths. Also validate trailer metadata and contain deferred trailer errors so invalid application-supplied values cannot escape as uncaught exceptions.