Mike_Ayers_1148
Jan 15, 2013Nimbostratus
HTTP Monitor Host Header
In building a monitor for pool members, I did a simple HTTP monitor that does a GET on /. Testing this with curl worked nicely and I chose a reponse matching string that should work well. However, the pool members were marked down, even though I was running the curl request at the same time.
More detailed testing showed that this server has some quirks, but the one that seems to apply in this case is that the Host header is required, or the server will not respond. Examining the bytestream I see that an HTTP monitor does not fill out the Host header, as required by RFC. I can not fill this out in the monitor definition, as the value is different for each pool member.
Am I missing something here?