HP 7102dl - ProCurve Secure Router Configuration Manual page 451

Response Class
5xx—Server Error
(The server failed to fulfill an
apparently valid request.)
As shown in Table 9-2, status codes in the 200 to 299 range indicate success.
You might configure a probe to accept only responses with these codes as
successful. Or you might configure the probe to accept any status that does
not actually indicate a server error.
To specify the acceptable status codes, from the network monitor probe
configuration mode context, enter:
Syntax: expect status <minimum> [<maximum>]
You can specify a single acceptable status by entering only the <minimum>
value. Or you can specify a range of acceptable statuses by entering both
<minimum> and <maximum> values; the range is inclusive. For example,
a valid range for a status indicating success would be from 200 to 299.
Requiring Particular Information from the Web Server. You can
require the Web server to return a message that matches a particular expected
string. For example, to verify that the probe reaches the correct Web server,
you configure the probe to test not just that the server sends any content, but
that it sends the correct content.
The characters that the request must include is specified by a set of keywords,
known as a regular expression. To configure the regular expression, from the
network monitor probe configuration mode context, enter:
Syntax: expect regex "<expression>"
Enclose the expression in quotation marks so that you can enter spaces.
For example, to allow the test to pass only if the words "Welcome to ProCurve"
is found in the Web server's response message, enter:
ProCurve(config-probe-MyWebServer)# expect regex "Welcome to ProCurve"
Response Status Code
• 500: Internal Server Error
• 501: Not Implemented
• 502: Bad Gateway
• 503: Service Unavailable
• 504: Gateway Timeout
• 505: HTTP Version Not Supported
• 509: Bandwidth Limit Exceeded
Network Monitoring
Configuring Network Monitoring
9-23