Forum Discussion
GavinW_29074
Nimbostratus
NimbostratusCatching 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,...
Michael_YatesNimbostratus
NimbostratusBasically the same way. Just find out what HTTP::status code it is throwing and handle it the same way. The HTTP::status handler can capture any status code: 200, 301, 302, 500, etc.
I would advise caution in handling too much though and suggest sticking with the status codes that report on hard failures or explicit behaviors (300's or 500's). The 200's and 400's are part of normal application behavior.