[ZBX-22001] Web scenario step fails to find pattern right after update ro 6.2.5 Created: 2022 Nov 30  Updated: 2024 Apr 10  Resolved: 2022 Dec 02

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Proxy (P), Server (S)
Affects Version/s: None
Fix Version/s: 6.0.12rc2, 6.2.6rc2, 6.4.0beta5, 6.4 (plan)

Type: Problem report Priority: Blocker
Reporter: Reza Jahed Assignee: dimir
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Ubuntu 22.04
Zabbix 6.2.5 nginx/postgresql

Issue Links:
Causes
caused by ZBX-21765 incorrect format for custom HTTP head... Closed
Team: Team A
Sprint: Sprint 95 (Dec 2022)
Story Points: 0.25

 Description   

Steps to reproduce:

Right after I upgraded from 6.2.4 to 6.2.5, one of our websites faced an issue. Zabbix is unable to find the specified patterns with the following error:

I believe this is due to zabbix being unable to decompress gzip, and is caused by ZBX-21765 fix.

 

More Info:

#curl -vsH 'Accept-encoding: gzip' http://1.1.1.1/Loader.aspx | gunzip -

  •   Trying 1.1.1.1:80...
  • Connected to 1.1.1.1 (1.1.1.1) port 80 (#0)
    > GET /Loader.aspx HTTP/1.1
    > Host: 1.1.1.1
    > User-Agent: curl/7.81.0
    > Accept: /
    > Accept-encoding: gzip
    >
  • Mark bundle as not supporting multiuse
    < HTTP/1.1 200 OK
    < Cache-Control: public, no-cache="Set-Cookie"
    < Content-Type: text/html; charset=utf-8
    < Content-Encoding: gzip
    < Expires: Wed, 30 Nov 2022 08:46:26 GMT
    < Server: Microsoft-IIS/10.0
    < Set-Cookie: ASP.NET_SessionId=nedlxcxms0iquhfblij2rp5k; domain=.example.com; path=/; HttpOnly; SameSite=Lax
    < Strict-Transport-Security: max-age=480; preload
    < Content-Security-policy: defult-Src 'self'
    < X-XSS-Protection:  1; mode=block
    < X-Farams-Options: DENY
    < X-Content-Type-Options: nosniff
    < X-Permitted-Cross-Domain-Policies: none
    < Date: Wed, 30 Nov 2022 08:46:14 GMT
    < Content-Length: 117130
    <
    { [11981 bytes data]
  • Connection #0 to host 1.1.1.1 left intact

 

 Comments   
Comment by dimir [ 2022 Dec 01 ]

That's right, caused by ZBX-21765.

In that issue user was complaining that the "Accept-Encoding" header that we set in every request was causing an error on the web server. We decided to remove it since Zabbix cannot guess which encodings should be set in the request. Since that fix was released Zabbix is not setting

Accept-Encoding: deflate, gzip, br

automatically anymore. It is now the responsibility of a user to set it in a web scenario configuration.

As for regression that was introduced, this is bad, I agree, one of the solutions would be to add these on every web scenario and every web scenario step where additional headers are set. To be discussed.

Comment by Vladislavs Sokurenko [ 2022 Dec 01 ]

Hmm, looks like it is mandatory for us to set it, otherwise decompression will not be performed automatically, can you please confirm ?
Confirmed, setting Accept-Encoding header does not enable compression,  ZBX-21765 should be reverted

Comment by dimir [ 2022 Dec 02 ]

Decision is to revert changes introduced in ZBX-21765

The fix will be available in this ticket.

Comment by dimir [ 2022 Dec 02 ]

Fixed in development branch feature/ZBX-22001-6.0

Comment by dimir [ 2022 Dec 02 ]

Fixed by reverting change introduced in ZBX-21765, in

Generated at Fri Apr 25 08:43:01 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.