An HTTP check sends a bounded GET request to the target URL and evaluates the response against the target configuration. It records the final URL, HTTP status, response duration, time to first byte, redirects and a bounded content summary.
Expected status range
Each HTTP target has an expected status range. The default range accepts normal 2xx and 3xx responses, but the target configuration can define another range when the endpoint has a deliberate response contract.
Redirects and safety
Redirects are handled one hop at a time and each destination is validated. WebCheck limits redirect depth, rejects restricted destinations and does not allow an HTTPS target to downgrade to HTTP through a redirect.
Timing and limits
WebCheck records total response duration and time to first byte. Requests have bounded connection and total timeouts, response-body limits and outbound-request limits. A slow response may be Degraded rather than Failed when it crosses the relevant threshold.
What an HTTP check cannot prove
A successful GET proves that this public request completed and met its configured response conditions. It does not prove that a user can log in, submit a form, complete checkout or reach the site from every network.