From spah@syntec.co.uk Wed Jun 24 08:24:22 2026 From: spah@syntec.co.uk To: xymon@xymon.com Subject: [Xymon] https URL in xymon recipient field causes 'Cannot resolve hostname' error Date: Fri, 13 Oct 2017 14:46:06 +0100 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4478124417296560145==" --===============4478124417296560145== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Hi to you all, It was suggested on this list recently that a way of getting Xymon client sending encrypted messages to the server using the currently Staple version would be to use *xymoncgimsg.cgi* on the web server over TLS. The xymon man page says one can use a URL in the recipient field for HTTP transport. There is no mention of HTTPS anyway in the man pages, but because it was suggested on the list I have tried it and it does not work: It seems to try and resolve https as hostname 'https' rather than interpreting it as a URL. For example: $ xymon https://www.google.com/xymon-cgi/xymoncgimsg.cgi "test" 2017-10-13 12:55:10.323994 Whoops ! Failed to send message (Cannot resolve hostname) 2017-10-13 12:55:10.324124 -> Cannot determine IP address of message recipient https $ xymon "https\://www.google.com/xymon-cgi/xymoncgimsg.cgi" "test" 2017-10-13 12:55:33.408007 Whoops ! Failed to send message (Cannot resolve hostname) 2017-10-13 12:55:33.408073 -> Cannot determine IP address of message recipient https\ I wonder if there is a trivial fix for this? P.S. Using plain old http does work: $ xymon http://www.google.com/xymon-cgi/xymoncgimsg.cgi "test" ... Many thanks, SebA --===============4478124417296560145==--