Retrieving the content of a web page through an HTTP Agent item is a common practice. However, one potential drawback of this approach is content blocking.
This occurs because the HTTP item check is executed by the Zabbix Server, and if the server is behind a blocking system, the web content may become unreachable.

A workaround exists when the web server provider has an active Zabbix Agent. In such cases, the "web.page.get" item can be employed to send the web content, bypassing a firewall and eliminating the need for unnecessary firewall rules.
This method may face limitations in scenarios where content requires header authentication, as the "web.page.get" item lacks options for handling header values.

Another usage of the "web.page.get" involves using a host monitored by an Agent as a makeshift web proxy. In this scenario, the Agent retrieves web content and forwards it to the Zabbix Server.

Presently, the Zabbix Agent lacks the capability to fetch web pages using HTTP header options. While some feature requests echo this need, they were closed as duplicates. Notably, issue ZBXNEXT-1816 garnered attention and discussion but was ultimately closed as a duplicate as well.

To address these limitations and enhance the capabilities of the Zabbix Agent, the inclusion of a parameter allowing the passage of basic header options would prove beneficial for users, broadening the Agent's functionality.

Something like this:

web.page.get[host,<path>,<port>,<header: value>]