Linux server (Debian, Gentoo)

Documentation page for the option: http://curl.haxx.se/libcurl/c/CURLOPT_ACCEPT_ENCODING.html .

I concur...

I was having issues with some web page I was monitoring returning "Compressed" pages (Content-Encoding: gzip), which I could not "match strings" to, the content being compressed and garbled in the zabbix_server logs.

Adding Maxim's change to the 2.4.3 source http_test.c file and recompiling fixed the issue for me. The web page is now being fetched properly and string matching works...

Thanks Maxim and Aleksandrs!

G.

Is there any news on this problem? In version 3.2, problem still there.

semochkinmv,

it's not on the roadmap yet.

Any chance this can make it's way onto the roadmap?
I think you will see the website monitoring portion gaining a-lot of attention if you haven't already. The industry as a whole doesn't seem to have any cost effective solutions in place as far as I have seen and the need for this sort of monitoring is rising very quickly.

Thanks,
J

joshuamcdo,

sure! By (co-)sponsoring development of this feature.

Marc,

In a sense I have tried to do just that by way to trying to get Zabbix into 2 different companies I have been with in a paid services capacity. That fell apart the first time and this last time we didn't get a response to the RFP. :/

joshuamcdo, how did you communicate ?

I've hit this problem too. Can we bump this issue up? I would rather use official RPMs then rebuild each release with the attached patch?

jsosic, the best bet to bump up a ZBXNEXT is contacting [email protected]

I just hit that issue when I started using Memcached cache with Nginx (on a Bitrix site it is called "composite mode"). The site I'm trying to monitor is compressed out of the box:

$ curl -s -X GET -I https://favor-group.ru | grep content-encoding
content-encoding: gzip 

I can read it with curl --compressed, but I can't set up a Web Check for that page using Zabbix Server 5.2.4. I'll need to alter the query params for a query not to hit the cache and return not gzipped answer, and I'll be checking the backend but won't check the scenario of Nginx retrieving answer from the Memcached.

I would be very grateful if the fix would make it to the upstream.

We are fixing it in 6.0 by allowing all encodings supported by cURL lib.

Available in:

• 5.0.18rc1 f461c79ebb0,  889750ef05f
• 6.0.0alpha5 (master) 3335c81a32a,  101769b5743

Temporary removed curl support from 6.0.0alpha5 agent packages on rhel 5 and 6, due to a bug introduced by this issue. Will restore it as soon as proper fix is merged.

Reverted. New releases should be back to normal again.

Documentation updated:

• What's new in 5.0.18
• What's new in 6.0