Feature #19717

Use PHP built–in gzip/deflate compression in Frontend

Added by Dmitry Dulepov almost 11 years ago. Updated about 9 years ago.

Status:
Closed
Priority:
Should have
Category:
Communication
Target version:
-
Start date:
2008-12-18
Due date:
% Done:

0%

PHP Version:
4.3
Tags:
Complexity:
Sprint Focus:

Description

Currently TYPO3 uses its own GZip compression class. This class was not changed for a long time and few know how it works. PHP includes its own output compression handler, which is not only faster but also maintained by PHP team and supports "deflate" compression in addition to "gzip".

The attached patch changes TYPO3 Frontend to use PHP handler instead of TYPO3 own. It will also correct "Content-length" header generated by "config.enableContentLengthHeader=1".

(issue imported from #M9974)

9974_v2.diff View (6.25 KB) Administrator Admin, 2009-02-01 15:30

9974_v4.diff View (8.46 KB) Administrator Admin, 2009-03-02 10:45


Related issues

Related to TYPO3 Core - Bug #20413: wrong content-length header breaks frontend in case of proxy-usage Closed 2009-05-10

History

#1 Updated by Dmitry Dulepov over 10 years ago

Another possible optimization: always send content length. It helps browser to detect the end of data stream aftser and speeds up rendering by 0.5-1s according to measurements with FireBug. It is especially helpful with pipelining or keep-alives enabled on the web server.

#2 Updated by Dmitry Dulepov over 10 years ago

Attached v4 of the patch as per discussion with Thorsten Kahler. The only change is: compression hook is moved to a separate class.

#3 Updated by Martin Kutschker over 10 years ago

According to ChangeLog this has been fixed on 4.3.2009

Also available in: Atom PDF