"Invalid HTTP header" and unsafe legacy renegotiation Errors in Web Monitoring

[cey.ozt]

Hello,

I'm getting following errors on two different web monitoring. Has anyone encountered these specific errors before?

Invalid HTTP header field was received: frame type: 1, stream: 1, name: [keep-alive], value: [timeout=5]

Failed: OpenSSL/3.0.13: error:0A000152:SSL routines::unsafe legacy renegotiation disabled

Thanks in advance for any ideas or guidance you can provide.

[Tymon]

Hi,

The first error seems to be caused by an incorrectly set HTTP header in web scenario. Could you provide screenshot or snippet showing the header configuration of your web scenario?

Going to the second issue it looks like OpenSSl is blocking TLS renegotiation. This could happen when the target server supports only legacy TLS renegotiation, which is disabled by default in OpenSSL3.x. You Can try enabling TLS 1.2 or higher on the target server .

[cey.ozt]

I will try enabling TLS, thanks for help. The first error actually works in an older version of zabbix but not work in 7.0.16 maybe it's issue in new version