HTTP Monitor and checking http headers

Hi Sean,

 

 

Thanks for posting your solution. I don't think the Connection header was implemented in HTTP 1.0, so you might be better off using HTTP 1.1 for the request. HTTP 1.1 requires a Host header, but not a value for it. If you don't want to specify the host header value, you can leave it blank:

 

 

GET / HTTP/1.1\r\nHost: \r\nConnection: Close\r\n

 

 

Also, bigd, the monitoring daemon, will add one or two carriage return / line feeds to the end of the send string (varying by version). It's worth it to verify for your particular version, whether your configured send string ends up having two and only two CRLF's at the end on the actual requests made to the pool members.

 

 

Aaron