Web request
HTTP Blocking
Intercepting and blocking unencrypted HTTP requests based on content.
Read the definitionThe definition and detection notes below retain the published reference wording. They are not a current network test.
01 / Definition
What it means.
HTTP blocking involves inspecting unencrypted web traffic and blocking requests based on URLs, headers, or content. Since HTTP transmits data in plaintext, network operators can see exactly what pages users request and selectively block access.
This technique is becoming less effective as HTTPS adoption increases, but remains relevant for legacy systems and in contexts where TLS is stripped or blocked entirely.
02 / How We Detect This
What we look for.
We make HTTP requests to test URLs and compare responses against expected content. Blocking is indicated by connection resets, redirects to block pages, injected content, or timeouts. We distinguish HTTP blocking from server-side issues by validating responses from control vantage points.
03 / Examples
What it can look like.
HTTP request returns government block page
Connection reset after HTTP GET request
Injected JavaScript redirecting to warning
Illustrative examples from the glossary, not incident reports or live observations.
Sources
Read the original.
Reference context & original shorthand
Published bypass label: Easy to bypass.
This is the original index’s editorial shorthand. Actual access depends on the network and technique; this label is not a guarantee. The glossary has no per-entry publication or review date.
Related links lead to definitions in the published glossary.
Complete definition →