Watchdog: HTTP Content
Checks the response body of a URL for expected or forbidden strings. Type http_content, runner Dashboard. Fields, defaults, statuses and messages.
Watchdog: HTTP Content
The check requests one of the client's URLs with GET and searches the response body for strings. The HTTP status code is recorded but does not affect the result. An error page with status 500 can therefore be OK if it contains the expected text.
| Property | Value |
|---|---|
| Type identifier | http_content |
| Runner | Dashboard |
| Target in the email | URL (label of the selected URL) |
Fields
| Field | Key | Default | Meaning |
|---|---|---|---|
| URL | client_url_id |
Required. One of the client's URLs | |
| Expected string | expected_string |
empty | String that must appear in the response body. Empty skips the test |
| Forbidden string | forbidden_string |
empty | String that must not appear. Empty skips the test |
| Timeout (seconds) | timeout |
10 |
Request time limit in seconds |
The search is case-sensitive and looks for a literal string, not a regular expression. BasicAuth credentials of the URL are sent along.
Behaviour
As with the HTTP check, the check verifies the TLS certificate and follows up to 5 redirects.
| Situation | Status | Message |
|---|---|---|
| Expected string missing | FAIL |
Expected string not found in response: "<text>" |
| Forbidden string found | FAIL |
Forbidden string found in response: "<text>" |
| Both tests passed | OK |
none |
| Connection, TLS or timeout error | FAIL |
Error text |
| No URL selected | UNKNOWN |
No URL selected for this check |
| URL was deleted | UNKNOWN |
URL #<id> not found — was it deleted? |
If both strings are empty the check is OK as soon as the URL answers. The expected string is tested first.