HTTP/1.1: Transfer-Encoding:identity is prohibited#2427
Closed
yadij wants to merge 1 commit into
Closed
Conversation
HTTP specification deprecated identity encoding but still allows its use when the Transfer-Encoding header is otherwise correctly used. Squid compliance update at the time kept accepting this encoding as it was being used by agents. However the HTTP specification explicitly requires that encoding to be wrapped within chunked encoding. The bare Transfer-Encoding:identity form is explicitly prohitibed with a MUST apply chunked requirement.
yadij
added
M-cleared-for-merge
squid-anubis
pushed a commit
that referenced
this pull request
Jun 2, 2026
HTTP specification deprecated identity encoding but still allows its use as an unknown encoding when the Transfer-Encoding header is otherwise correctly used. Squid compliance update at the time kept accepting identity encoding as it was being used by agents. The form supported was Transfer-Encoding:identity. However, the HTTP specification explicitly requires that any encoding MUST be wrapped within chunked encoding. As such the bare Transfer-Encoding:identity form Squid accepted is explicitly prohibited. The correct Transfer-Encoding:identity,chunked syntax has been rejected by Squid for nearly 5 years already without complaint. So support is being dropped entirely here.
squid-anubis
added
the
M-waiting-staging-checks
squid-anubis
added
M-merged
yadij
removed
the
S-could-use-an-approval
squidadm
removed
the
backport-to-v7
Collaborator
|
queued for backport to v7 |
Closed
kinkie
pushed a commit
that referenced
this pull request
Jun 2, 2026
HTTP specification deprecated identity encoding but still allows its use as an unknown encoding when the Transfer-Encoding header is otherwise correctly used. Squid compliance update at the time kept accepting identity encoding as it was being used by agents. The form supported was Transfer-Encoding:identity. However, the HTTP specification explicitly requires that any encoding MUST be wrapped within chunked encoding. As such the bare Transfer-Encoding:identity form Squid accepted is explicitly prohibited. The correct Transfer-Encoding:identity,chunked syntax has been rejected by Squid for nearly 5 years already without complaint. So support is being dropped entirely here.
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
4 participants
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.
HTTP specification deprecated identity encoding but still allows
its use as an unknown encoding when the Transfer-Encoding
header is otherwise correctly used.
Squid compliance update at the time kept accepting identity
encoding as it was being used by agents. The form supported was
Transfer-Encoding:identity.
However, the HTTP specification explicitly requires that any
encoding MUST be wrapped within chunked encoding.
As such the bare Transfer-Encoding:identity form Squid accepted
is explicitly prohibited.
The correct Transfer-Encoding:identity,chunked syntax has been
rejected by Squid for nearly 5 years already without complaint.
So support is being dropped entirely here.