Forum Discussion
Bastien_8356
Nimbostratus
NimbostratusHTTP health monitor generate an apache error
Hi,
I configure the basic http health monitor (GET /\n\r) on my web servers, I have this in my apache error log :
[Thu Jul 14 13:39:44 2011] [error] [client x.x.x.x] Attempt to se...
Hamish
Cirrocumulus
CirrocumulusYes. HTTP/1.1 included the previously optional host header as a mandatory item. For monitors it's not really worthwhile going to HTTP/1.1 (Unless you have some strange server that requires it :), as the monitor can't add the host header dynamically (Sadly), so you have to create a new monitor every time (It would be nice if you could specify a FQDN in a VS for attached monitors, but that creates problems in itself as monitors are attached to pools and not VS's.... That would possibly require re-architecting so you could instantiate a monitor per VS:Pool pairing... And have different poolmember status per attached VS... Or just a FQDN per pool maybe to use on the monitor...
Sorry... Rambling out loud again...
H
