-
New Feature Request
-
Resolution: Fixed
-
Major
-
None
-
Sprint 50 (Mar 2019), Sprint 51 (Apr 2019), Sprint 52 (May 2019), Sprint 53 (Jun 2019)
-
3
One of our biggest problems could be solved if web.page.regexp were also capable of doing SSL, precisely because it is templatable:
web.page.regexp[{HOSTNAME},PATH,80,STRING,6]
But this only works for non-ssl ports. We use such similar PATHs that we could easily extend Zabbix to use Discovery (not with this string) alongside our other discovered information to use templates to assign web checks.
We need a flag to the existing web.page.regexp (for http or https) or could you perhaps clone this built-in key and make the clone SSL capable? Something like web.page.ssl.regexp? This would potentially solve HUGE amounts of stress with simple web tests for which the scenarios are overkill.
We need it to not be merely port dependent as we have many non-standard ports listening on SSL.