Bug #65719
closedFE content-length header set too early
100%
Description
With 6.2, sending content-length header was enabled by default via config.enableContentLengthHeader considered as "on".
This is done in TSFE->processOutput. Unfortunately, there are a couple of things calculated after this header length is set - and some of those tend to change the output and thus its length afterward. Most prominently the eofe hook. If so, the content length will is set to a wrong value and some webservers or proxies stumble upon that - eg. varnish is a bit picky if header length and actual length differ.
Maybe possible solution: Move the header sending out of processOutput to a later point in TSFE processing - maybe directly before the echo out? That would be more clean and all the "disable if debug and disable if beUserLogin" and all this stuff would be obsolete.
Updated by Tymoteusz Motylewski over 7 years ago
- Related to Bug #76100: Design problem with sending of header "Content-Length" added
Updated by Gerrit Code Review about 7 years ago
- Status changed from New to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/54268
Updated by Gerrit Code Review about 7 years ago
Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/54268
Updated by Gerrit Code Review about 7 years ago
Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/54268
Updated by Gerrit Code Review about 7 years ago
Patch set 1 for branch TYPO3_8-7 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/54269
Updated by Benni Mack about 7 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset a7d63adc3b4d568dee86fe9267b1b069c089269f.