Content-length wrong with zlib.output_compression = On

[simix]

I've just tested current 1.8.4rc1 snapshot and there is a problem with Content-length being wrong if PHP is configured with "zlib.output_compression = On". Content-length calculated in Zabbix is wrong because of the output compression applied later.
In my situation the following stack doesn't work:
Apache/PHP -> Pound -> Inet -> Squid -> Firefox

Attached patch fixed it for me. I've just commented out the Content-length header. A Google search told me that doing this correctly in PHP is not very easy. Does it hurt to remove the Content-length header?

[richlv]

i suspect this might have something to do with javascript caching. of course, breaking compression is not that great... please, report this on the tracker. i guess this was working as expected in 1.8.3, right ?

[Palmertree]

Also had to do the same with https and Apache.

[simix]

I posted the issue here

https://support.zabbix.com/browse/ZBX-3118

@richlv: Yes it was working with 1.8.3 IIRC. The issue is not directly related to caching but with the new headers being sent. One of them is Cache-Control, which works fine, another is Content-length which can not be sent that way if output compression is on.

[Aly]

Should be fixed.