I changed the expect status value as below

probe http TEST-HTTP

interval 30

passdetect interval 10

request method head

expect status 302 302

The probe is still failing with the log message

Apr 20 2009 12:04:35 : %ACE-3-251010: Health probe failed for server 192.168.1.10 on port 80, received invalid status code

On 'show probe detail' it shows the last status code as 400 which means Bad Request

--------------------- probe results --------------------

probe association probed-address probes failed passed health

------------------- ---------------+----------+----------+----------+-------

serverfarm : TEST-APP

real : TEST-SERVER1[80]

192.168.1.10 27 27 0 FAILED

Socket state : CLOSED

No. Passed states : 0 No. Failed states : 1

No. Probes skipped : 0 Last status code : 400

No. Out of Sockets : 0 No. Internal error: 0

Last disconnect err : Received invalid status code

Last probe time : Mon Apr 20 12:05:33 2009

Last fail time : Mon Apr 20 12:00:53 2009

Last active time : Never

The http page is showing perfectly on the web browser. Also, using the http head/get tool, I can see that 302 is returned.

What could be the problem.

Regards.

Hi,

shouldn't you specify the url of the page the ACE should get (head)?

fe: request method head url /index.html

Hi,

I have entered request 'request method head url /' which shows in the running config as 'request method head' i.e. default.

Using index.html etc is not mandatory I believe as '/' checks for any web service.

Hi,

I found this in the config guide for probing:

"By default, the HTTP request method is a GET with the URL “/”. If you do not configure a URL, the probe functions as a TCP probe."

Is your server listening to another port then 80?

Yes, the service is running. If I do a telnet on port 80 it opens up. The head/get utility is coming back with 302. And the page is showing on the web browser.

I sniffed the traffic going to the rserver and noticed invalid SYN request to the webserver i.e. I don't see '/' request in the packet capture. Below is the serverfarm config

serverfarm host TEST-APP

rserver TEST-SERVER1 80

probe TEST-HTTP

inservice

However, similar probe is working fine in admin context on another rserver. The only difference is that the probe is on a custom HTTP port and not default port 80. Can that cause a difference.

To add onto the above, the web server is on IIS 6.0 (Windows Server 2003) and the error returned on the probe is HTTP 400 - Bad Request (Invalid Hostname).

Has anyone experienced this ?

I had similar problems with an AS 400.

Had to configure the host.

So I prefere to use the expect 400