For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Valentine_96813's avatar
Valentine_96813
Icon for Nimbostratus rankNimbostratus
Jun 19, 2012

HTTP 1.1 monitor multiple instances

I have a need to replace current multiple monitors with one instance of an HTTP. All of the gets resolve to the same page, however, the domains are different. Basically, I am looking for //login.html but, the domain could be abc.com or def.com or ghi.com.

 

 

I read the sol article on creating HTTP monitors sol2167. It states 'However, in an HTTP 1.1 request, the Host header is required, although it may contain a null value.'

 

 

I take this to mean that the value can be anything and does not matter meaning I could something like www.123.com in the get string for all different pools I have like below. Is this the case?

 

 

GET //login.html HTTP/1.1\r\nHost:www.123.com \r\nConnection:Close\r\n

 

management
monitoring

1 Reply

  • hoolio's avatar
    hoolio
    Icon for Cirrostratus rankCirrostratus
    Jun 26, 2012
    Hi Valentine,

     

     

    If your web applications require a specific host header you'll need to create one monitor per host header. If they'll accept any host header you could specify a null host header value in an HTTP 1.1 send string or not specify the host header at all and use an HTTP 1.0 request:

     

     

    HTTP 1.0:

     

    GET /login.html HTTP/1.0\r\nConnection: close\r\n\r\n

     

     

    HTTP 1.1:

     

    GET /login.html HTTP/1.1\r\nConnection: close\r\nHost: \r\n\r\n

     

     

    Aaron