On Thu, Nov 3, 2011 at 12:14 PM, Darrik Mazey <darrik.lists at darmasoft.com>wrote:
On 11/03/2011 12:26 AM, Ralph Mitchell wrote:
Giving:
192.168.1.4I get an Apache log entry. Changing that to
192.168.1.4/ <http://192.168.1.4/>I get NO Apache log entry, nothing at all. Adding xymon to the end:
192.168.1.4/xymon <http://192.168.1.4/xymon>gets me green status and a log entry again.
Are you assuming that Xymon is installed at the top level, or are you appending anything to the hostname??
Technically speaking, I make the assumption that xymon is installed top-level. To get the page (depending on version of xymon and assuming ssl is checked) I basically do:
https://<HOSTNAME_SETTING>/nongreen.html
Where HOSTNAME_SETTING is "192.168.1.4/", this gives a request for:
https://192.168.1.4//nongreen.html
The apache Http module kicks up a Bad URI error on a double slash.
If xymon is not installed top-level, HOSTNAME_SETTING can be set to "192.168.1.4/PATH" (no trailing slash) and the request becomes:
https://192.168.1.4/PATH/nongreen.html
I will update the code to check for a trailing slash in the hostname and remove it, as a convenience.
Do you recommend a separate setting for the PATH part, or is it sufficient to append that to the hostname setting?
Perhaps just a note in the hostname setting box? Could it be labelled something like "Hostname and path", or just "Url for xymon"?
Ralph Mitchell