Forum Discussion
Nimbostratushttp health check monitor
Understand that http health check monitor support is http0.9 by default, please advise which is more recommended http0.9 or http1.1?
8 Replies
cjuniorNacreous
I suppose that if your server supports HTTP 0.9 and your monitor doesn't have to do more than a GET on a single web that is on the server, I see no problem in using a simple monitor like this.
Now, if this have more than one site bind on the server or needs to better monitor a "real" user connection, e.g. http headers, I should use the HTTP 1.1.
Have you seen this? https://support.f5.com/kb/en-us/solutions/public/2000/100/sol2167.html
That's just my opinion, tks
dw_888_212625If load balancing for various virtual servers with various web applications which some might support HTTP 0.9 or TTP 1.1, what would be more recommanded? can we say that using HTTP 1.1 is competible even for application that support HTTP 0.9? Any impact of we do global change for modifying the current http health check from htp 0.9 to http1.1 ?
- cjunior
- I always prefer simulate user navigation, so, would use HTTP 1.1, properly configured.
- What kind of access you provide? I don't know about browsers using earlier versions.
- May have some impact if, for example, you forgot to send the "Connection: Close" header. I honestly can see more advantages when it refines a monitor.
I do not know if I helped, I hope so!
Regards.
- dw_888_212625
unfortunately we do not have visibility on the type of access for the various customers. Base on http://www.ietf.org/rfc/rfc2616.txt, it mentioned that for HTTP1.1 Compatibility with Previous Versions Kindly advise if we can be assured that there won't be any impact base on this? Can we confirm that HTTP1.1 is more stable and recommanded in the industry standard now? we had a similar UAT setup which is same as this production, but it is not facing the issue which we reported. kindly advise.
- dw_888_212625
Cjunior / anyone can help advise please?
- cjuniorSorry for delay, If we're just talking about monitoring a http, I think the most important thing is to ensure that the service is really UP. If you are in doubt about which http version is better to make a request to the server, please keep in mind that the Big-IP just makes a request and than the server will process it. So, Big-IP will wait for a positive or negative reply for the request which It have made. I don´t want to go deeper about the difference between http versions because for BIG IP it is transparent, since the service behaviour depends on platform where the service runs (apache, IIS, etc.) So, if a simple get is enought, a simple http 0.9 request should be useful.
- dw_888_212625
thanks for your reply. will you be able to advise on the situation that all along, we were using health monitoring http80, then suddenly this monitoring shows disabled, and we change the health monitoring to tcp, and it shows enabled, and the issue was resolved. Any idea any possible cause?
- cjuniorIf the tcp monitor shows UP and http monitor shows DOWN, there are some possibilities e.g.: HTTP service is absent on tcp port 80, HTTP monitor parameters are incorrect, etc. If you can access the website resources, means that http monitor parameters are probably wrong (e.g. "Receive String") or server responses are intermitent for the requests. Regards.
