The resource is temporarily at the URL in the Location header; keep using the original URL.
302 Found is a temporary redirect: the client should follow Location for this request but keep requesting the original URI later. Search engines keep the original URL indexed. Browsers change POST to GET when following a 302 (behaviour RFC 9110 now allows), which is why 303 and 307 exist to make intent explicit. 302 is not cached unless Cache-Control or Expires says so.
redirect(), Express res.redirect(), Django redirect(), PHP header('Location: ...').curl -sIL.| Header | Role |
|---|---|
Location | Temporary target URL. |
Set-Cookie | Often set alongside login redirects. |
HTTP/1.1 302 Found
Location: /login?next=%2Fdashboard
Content-Length: 0
Checking a whole domain's redirects? The HTTP status checker follows http, https, www and non-www variants and shows every hop.