Problem description: The following Valgrind errors are observed for Active proxy when it monitors a Zabbix server with a web scenario that has a failing step due to required string missing on URL:

==00:00:04:48.999 84621== 59 errors in context 1 of 1:
==00:00:04:48.999 84621== Conditional jump or move depends on uninitialised value(s)
==00:00:04:48.999 84621==    at 0x2A0BAE: zbx_recv_response (comms.c:323)
==00:00:04:48.999 84621==    by 0x2A0E19: put_data_to_server (comms.c:198)
==00:00:04:48.999 84621==    by 0x19B13B: proxy_data_sender (datasender.c:195)
==00:00:04:48.999 84621==    by 0x19B571: datasender_thread (datasender.c:302)
==00:00:04:48.999 84621==    by 0x2815F3: zbx_thread_start (threads.c:124)
==00:00:04:48.999 84621==    by 0x16D73D: MAIN_ZABBIX_ENTRY (proxy.c:1333)
==00:00:04:48.999 84621==    by 0x27BEAC: daemon_start (daemon.c:443)
==00:00:04:48.999 84621==    by 0x16577B: main (proxy.c:1057)
==00:00:04:48.999 84621==  Uninitialised value was created by a stack allocation
==00:00:04:48.999 84621==    at 0x2A0B00: zbx_recv_response (comms.c:287)
==00:00:04:48.999 84621== 
==00:00:04:48.999 84621== ERROR SUMMARY: 59 errors from 1 contexts (suppressed: 0 from 0)

P.S. The error is not observer for Zabbix server

Steps to reproduce (at least that's how I got the error, not sure which exact actions caused the errors):

1. Have a fresh Zabbix 6.0 or younger instance
2. Bring up Zabbix server and an active Zabbix proxy
3. Naigate to Administration => Proxies and create the corresponding active proxy in frontend
4. Wait for proxy to be seen
5. Export Zabbix server host and rename the original zabbix server (for example to Zabbix server original)
6. Import the previously exported zabbix server and set it to be monitored by the active proxy
7. Wait for the imported server to start collecting data
8. Add a Web scenario (with Agent = Firefox 73 (Linux)) to the imported server that would have a step with the following parameters:
   1. URL: https:
      ss.lv
   2. Required string: Vieglie auto
   3. Required status codes: 200
9. Wait for the web scenario step to fail
10. Update web scenario step - set Required status codes to 301
11. Wait for the scenario step to fail with another error
12. Check Proxy Valgrind logs

Result: the above mentioned errors are observer in the Valgring log for proxy
Expected: no "Conditional jump or move depends on uninitialised value" errors should be found in Valgrind logs

Valgrind log for 6.0: zabbix_proxy_VALGRIND_01062023_60.zip
Zabbix proxy log for 6.0: zabbix_proxy_6_0.log

Valgring log for 7.0: zabbix_proxy_VALGRIND_01062023_master.zip
Zabbix proxy log for 7.0: zabbix_proxy_master.log