Project

General

Profile

Actions

Bug #65719

closed

FE content-length header set too early

Added by Christian Kuhn over 9 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Frontend
Target version:
-
Start date:
2015-03-13
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
Tags:
Complexity:
medium
Is Regression:
No
Sprint Focus:

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.


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Feature #19732: Enable "Content-length" header by defaultClosed2008-12-22

Actions
Related to TYPO3 Core - Bug #76100: Design problem with sending of header "Content-Length"Closed2016-05-09

Actions
Actions

Also available in: Atom PDF