Removes transfer-encoding header from responses with non compliant status codes #151
Conversation
This file contains 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
jhonndabi
changed the title
|
Hi @tallarium-bot @mwhitworth @Fedjmike! This seems pretty straight-forward and important for being more conformant with the spec. Do you think this can be merged and released? |
jhonndabi
deleted the
fix/removes-transfer-encoding-header-from-non-compliant-statuses
branch
jhonndabi
restored the
fix/removes-transfer-encoding-header-from-non-compliant-statuses
branch
jhonndabi
deleted the
fix/removes-transfer-encoding-header-from-non-compliant-statuses
branch
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.
Transfer-Encoding header violates RFC 7230:
https://datatracker.ietf.org/doc/html/rfc7230#section-3.3.1
We are having trouble to update our service mesh, because the new version are dropping requests, that are not compliant with the HTTP spec.
And I think this PR also resolves this issue #36