Account Links: Cart | Your Account | Logout

Skip to content

Red Hat Knowledgebase

Red Hat Knowledgebase Search:

Updated Within the Last:

New Solutions within the last day New Solutions within the last week New Solutions within the last month

Browse by topics:


Click to View a Topic
Red Hat Applications > Command Center > Issue <<  16 of 119 >>

Solution Tools:


Email a Solution Postcard Printer version Submit a comment on this answer Update notifications Request an answer Back

Article Reference

Article ID: 9135
Last update: 09-28-06
Issue:
What HTTP codes will cause a URL transaction check to report as CRITICAL?
Resolution:

The official policy for HTTP is:

2** - Success
3** - Redirection
4** - Client Error
5** - Server Error

Accordingly, response codes in the range from 300 to 399 are treated by following the ('GET') redirect to an eventual non-3** response. The eventual response is then evaluated based on the following two rules:

  1. Response codes in the range from 200 to 299 represent a "success" response from the server and are accordingly associated with an "OK" status. The configured checks are then applied to determine the final outcome of the check.
  2. Response codes greater than or equal to 400 represent an "error" response from the server and are accordingly associated with a "Critical" status. No further checks are applied.


How well did this entry answer your question?


good wrong incomplete out of date
Red Hat Applications > Command Center > Issue <<   16  of  119  >>