As an user who develops a (complex) web monitoring scenario, I would like a way to inspect the data that Zabbix/cURL a) sends to the target system and b) receives from the target system.

At the moment this is only possible by cranking up the log level to 5/TRACE, manually searching around in a huge log file for "process_httptest" and then wade through other unrelated noise from other threads. This is both unwieldy to use and can lead to a filled disk on the proxy/server if the user forgets to reset the log level after finishing development.

The reason for this requirement is that when developing tests against complex multi-step forms it is very easy to forget a required field or mess up a value requirement (e.g. typos in variable names leading to wrong expansion). While for plain HTTP forms one can have limited visibility via tcpdump or other packet inspection, proper HTTPS removes this ability.

The simplest way would be to implement support for an additional logfile, where the code in src/zabbix_server/httppoller/httptest.c can dump the raw request/response to; the best way (in my opinion) would be to stream it into the database alongside the "content size"/"loading speed" metric so that it can be retrieved from the UI.