Forum Discussion

GavinW_29074's avatar
GavinW_29074
Icon for Nimbostratus rankNimbostratus
Sep 27, 2011

Catching Timeout and HTTP 502/503 Errors

Hi there,     Next question... One of the items that we've got set-up on our current Apache set-up is the ability to catch a 502 "Bad Gateway" and 503 "Service Unavailable" and return a 'Sorry,...
application delivery
dev
devops
iRules
Michael_Yates's avatar
Michael_Yates
Icon for Nimbostratus rankNimbostratus
Sep 27, 2011
Hi GavinW,

 

 

The TCP Profile does not care about the availability of the "Content" being served by an application. It only checks to see that there is a "Service" listening on that port and responding. So as long as apache is alive and well the BigIP will keep sending traffic to it even if the application is in flames.

 

 

I would suggest an HTTP or HTTPS Health Check. You can set them to dig as deeply into the site as you wish to verify the availability of your application.

 

 

The F5 can either do a redirect or even provide a custom response itself when it sees an HTTP Status code that you tell it to look for. You can get more information on the HTTP::status command in the HTTP_RESPONSE event here:

 

 

http://devcentral.f5.com/wiki/iRules.HTTP__status.ashx

 

 

Hope this helps.