Forum Discussion
Dean_M_21414
Nimbostratus
NimbostratusIssue with GET in monitor
Hi all,
We have several IIS6 webservers, each with multiple sites, all using the same IP and port (80), being differentiated by host headers.
When we create an HTTP monitor on the Pool, using port 80 and a send string of GET /\r\n, the monitor shows the pool as being unavailable. However, when we use GET /HTTP1.1\r\n or GET /HTTP1.0\r\n the monitor shows the pool as available.
Why the difference, and what are the limitaitons of using either of the HTTP1.x qualifiers above, vs not using them, i.e. just GET /\r\n?
Regards
Dean
1 Reply
- Hi Dean,
I tested 'GET /' without any HTTP version specification against a default IIS 6.1 deployment and didn't have any issues:% telnet 10.0.0.12 80 Trying 10.0.0.12... Connected to 10.0.0.12. Escape character is '^]'. GET / Test page Test Connection closed by foreign host.
If you are running name-based virtual hosts, then you'll need to specify HTTP/1.1 as 'host' headers weren't introduced until version 1.1. I wrote an article a while back on better HTTP monitors (kind of a misleading title): http://devcentral.f5.com/weblogs/watkins/archive/2010/08/18/clean-up-those-webaccelerator-performance-reports.aspx
If you want a plethora of information on the differences between HTTP/1.0 and 1.1, look here: http://www8.org/w8-papers/5c-protocols/key/key.html
Hope this helps,
George
