HTTP 302 Found indicates the requested resource is temporarily available at a different URI provided in the Location header. The client should continue to use the original URI for future requests. Search engines do not transfer link equity for 302 redirects.
Status
302 FoundExample
GET /sale HTTP/1.1
Host: www.example.com
User-Agent: Mozilla/5.0
Accept: text/htmlHTTP/1.1 302 Found
Location: /sale/summer-2026
Content-Type: text/html; charset=utf-8
Content-Length: 151
<!doctype html>
<html>
<body>
<h1>Found</h1>
<p>This page is temporarily at <a href="/sale/summer-2026">/sale/summer-2026</a>.</p>
</body>
</html>How to Troubleshoot
Check if this should be a 301
If the redirect is permanent, use 301 instead of 302 to preserve SEO value.
Follow the redirect
Check the Location header for the temporary URL.
curl -I https://example.com/page
Check for redirect loops
Ensure the target URL does not redirect back to the original URL.
curl -L -v -o /dev/null https://example.com/page 2>&1 | grep 'Location:'
Common Causes
Temporary redirect for maintenance or testing
highThe resource is temporarily served from a different URL during maintenance, A/B testing, or while a feature is being rolled out.
Login redirect
highUnauthenticated users are temporarily redirected to a login page before being sent back to the original URL.
Related Status Codes
References
| Specification | Section |
|---|---|
| HTTP Semantics | RFC 9110 §15.4.3 |
Frequently Asked Questions
This reference was compiled from official RFCs, protocol specifications, and hands-on troubleshooting experience. AI tools were used primarily for formatting and organizing the content on the page.