Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

ACE http probe "request method type" mandatory on A3(2.6)?

Hi people,

I recently upgraded to A3(2.6) from A3(2.0) and I don't see the N/A option on the http probe "request method type".

It also has an asterisk * which means it's mandatory.

I tried to set up a new http probe for another farm I am creating and the probe shows status failed, although I can ping and telnet to the http server on port 80 from the ACE context. My probe is like that:

probe http http_probe_WWW
  interval 15
  passdetect interval 60
  expect status 200 200
  open 10

My other http probes for other farms work ok after the upgrade and they are similar.

So my question is: Do I need to set the request method type or something else causes the probe to fail?

thanks a lot.

George

Everyone's tags (6)
1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Re: ACE http probe "request method type" mandatory on A3(2.6)?

What you see is a problem with the GUI.

CSCtg78008    while creating http probe default method slected should be get as in CLI

But the request-method is not required.

So your config should work.

Do a 'show probe detail' to see the failure reason.

Get a sniffer trace as well.

Regards,

Gilles.

2 REPLIES
Cisco Employee

Re: ACE http probe "request method type" mandatory on A3(2.6)?

What you see is a problem with the GUI.

CSCtg78008    while creating http probe default method slected should be get as in CLI

But the request-method is not required.

So your config should work.

Do a 'show probe detail' to see the failure reason.

Get a sniffer trace as well.

Regards,

Gilles.

New Member

Re: ACE http probe "request method type" mandatory on A3(2.6)?

Gilles thanks a lot once more.

The problem was that the server was sending a status code of 302.

I added this to the list of expect codes, and now it's ok.

George

962
Views
0
Helpful
2
Replies