[TYPO3-core] RFC: #11063: wrong content-length header breaks frontend in case of proxy-usage
Dmitry Dulepov
dmitry.dulepov at gmail.com
Mon May 11 14:42:23 CEST 2009
Hi!
georg kuehnberger wrote:
> Problem:
> class.tslib_fe.php, function processOutput() calculates the
> content-length wrongly in case of enabled debug. this leads proxies to
> not deliver the complete page, but cut it off in the middle of nowhere.
>
> Solution:
> In case debug is activated, TYPO3 should not send content-length at all;
> proxies will behave nice then and deliver the complete page.
This solution will work but there is a better one: create the header later (after the debug, at the end of index_ts.php). It will allow content-length header for any kind of pages, so this will not be necessary:
==========
+ !$this->isEXTincScript() &&
+ !$this->beUserLogin &&
+ !$this->TYPO3_CONF_VARS['FE']['debug'] &&
+ !$this->config['config']['debug'] &&
+ !$this->doWorkspacePreview()
==========
Having content-length speeds up page loading in many browsers.
--
Dmitry Dulepov
In the TYPO3 blog: http://dmitry-dulepov.com/article/cleaning-your-apple-mighty-mouse.html
LinkedIn: http://www.linkedin.com/in/dmitrydulepov
Twitter: http://twitter.com/dmitryd
Skype: liels_bugs
More information about the TYPO3-team-core
mailing list