Forum Discussion
DNG_23691
Nimbostratus
Nimbostratus.NET vs. HTML Basic Monitoring
Problem: I can use a basic http monitor to query a .html page and get a response text with no issue. However, if I use a .NET page (.aspx) it will fail. The response text in the browser is correct, but the underlying code returned on the page must not be. Can't figure it out.
Monitor details:
GET /ck.cfm HTTP/1.1\nHOST:www.xyz.com\nConnection: Close\n\n
Returns Hello in the browser and Hello in the source of the return.
GET /HealthCheck.aspx HTTP/1.1\nHOST:www.xyz.com\nConnection: Close\n\n
Returns Hello in the browser but returns this in the source:
<br> Health Check Page <br>
name="form1" method="post" action="HealthCheck.aspx" id="form1">
Hello
Can't be sure what's going on.
Any thoughts?
hoolioCirrostratus
Hi,
Are you saying that HTML is what you see in the response from the health monitor? If so, that looks correct. The Hello text and the other HTML is rendered by the browser as Hello. Does the monitor correctly mark the pool member up?
If not, can you clarify what the issue is?
Thanks,
Aaron
DNG_23691Sorry I wasn't clear.
The ck.cfm file returns just the text Hello both in the browser view and when you view the source of the browser view.
The .aspx page returns the text Hello only in the browser view. The view source shows the code above. The F5 is marking the .aspx monitor as down.- hoolioIf you enable bigd debug (b db bigd.debug enable / disable) and check the log file (/var/log/bigdlog), do you see a valid response being marked as failed? What does the debug log show for the response which should contain "Hello"?
RFC2616 states the delimiter between HTTP header lines is a \r\n not just \n. Depending on version, bigd automatically appends one or two \r\n's to the send string before sending it to the pool members. Could you try changing the send string to:
GET /HealthCheck.aspx HTTP/1.1\r\nHOST:www.xyz.com\r\nConnection: Close\r\n
or
GET /HealthCheck.aspx HTTP/1.1\r\nHOST:www.xyz.com\r\nConnection: Close
Aaron - DNG_23691I'm sorry, after reviewing this more closely, I found I was using the wrong URL in the monitor. Its working fine. Thanks for responding.