]> git.ipfire.org Git - thirdparty/squid.git/commit
Allow 1xx and 204 responses with Transfer-Encoding headers (#769)
authorAlex Rousskov <rousskov@measurement-factory.com>
Mon, 8 Feb 2021 22:49:42 +0000 (22:49 +0000)
committerSquid Anubis <squid-anubis@squid-cache.org>
Wed, 10 Feb 2021 22:51:45 +0000 (22:51 +0000)
commitc64d8e60a3f04951509929c03ab57d99b2c068e7
treea0705b6efa1bdf5ae415ce2d04a533fe6d50520c
parent5f37a71acd0d24c3713316a06401a72e9f3194bc
Allow 1xx and 204 responses with Transfer-Encoding headers (#769)

HTTP servers MUST NOT send those header fields in those responses, but
some do, possibly because they compute the same basic headers for all
responses, regardless of the status code. Item 1 in RFC 7230 Section
3.3.3 is very clear about message framing in these cases. We have been
ignoring Content-Length under the same conditions since at least 2018.
We should be consistent and apply the same logic to Transfer-Encoding.

I also polished the Transfer-Encoding handling comment for clarity sake.
src/HttpHeader.cc