← Back to status codes
HTTP Status Code
302 Found
RedirectionThe resource is temporarily available under a different URL.
HTTP status code reference, response example, common causes, fixes, and related status codes.
What does HTTP 302 Found mean?
HTTP 302 Found is a status code sent by a server to indicate the result of an HTTP request.
Status codes help browsers, APIs, apps, and backend systems understand whether a request succeeded, failed, was redirected, or needs additional action.
In practice, HTTP 302 Found usually appears when a server responds under specific request, validation, permission, or infrastructure conditions.
Response example
HTTP/1.1 302 Found Location: /login
HTTP example
HTTP/1.1 302 Found
Relevant headers
Location
Location: /login
Common causes
- Temporary redirect
- Auth flow redirect
- Short-term routing change
How to fix it
- Use 301 or 308 if the redirect is permanent
- Check redirect logic in middleware or backend code
Common mistakes
- Assuming the status code alone explains the full backend issue
- Ignoring related response headers that add important context
- Treating temporary errors as permanent failures
- Retrying too aggressively without checking the cause
- Debugging the frontend only when the problem is server-side
How browsers and APIs use it
Browsers, APIs, and backend services use HTTP status codes to understand the outcome of a request. Depending on the status code, an application may render content, retry a request, redirect the user, show an error, or trigger a different flow in the client or server.
Developer note
Many login flows and middleware redirects use 302. If redirect behavior feels wrong, inspect the response chain in your browser devtools.