Expand description
Does plain HTTP upgrade to HTTPS?
One SSRF-guarded GET to http://<host>/, following redirects manually
(every hop re-validated, at most 5) without reading a body, then a pure
assessment of the redirect chain: an upgrade is a chain that ends on
https:// at the same registrable domain. A connection failure on the
first hop means nothing listens on port 80 (listening: false) — which is
fine, not a finding. A failure on a later hop does not erase what the
chain already shows once it has reached https:// or left the site; a
failed plain-http hop on the same site leaves the answer unknown (an
error). IP literals compare exactly, never through the PSL.
Single-attempt, like every probe.
Structs§
- Https
Upgrade Report - The outcome of an HTTP→HTTPS upgrade check.
Functions§
- check_
https_ upgrade - Probes
http://<host>/and reports whether it upgrades to HTTPS.