307 Temporary Redirect
Like 302, but guarantees the HTTP method is preserved. If a POST request gets a 307, the client should re-POST to the new URL, not switch to GET. This makes it safe for API redirects where the method matters.
What can I do?
- Your browser should follow the redirect automatically — wait a moment.
- If you see a redirect loop, clear your browser cache and cookies, then try again.
- Update any saved bookmarks to the new URL shown in your address bar.
How to debug & fix
- Prefer 307 over 302 when you need the HTTP method preserved
- For permanent redirects that preserve method, use 308
- Useful for POST-to-POST redirects (rare but valid)
- Test that your HTTP client re-issues the original method (POST/PUT) on the redirect target, not GET.
Code Example
res.redirect(307, '/api/v2/endpoint');
Related Status Codes
How HTTP Status Codes Work
Every HTTP response carries a three-digit status code that tells the client — browser, API consumer, or search-engine crawler — exactly what happened. The first digit defines the class: 1xx informational (request in progress), 2xx success, 3xx redirection, 4xx client error (bad request, missing auth, not found), and 5xx server failure.
Status codes are standardised in RFC 9110 (HTTP Semantics, 2022). Extensions like WebDAV (RFC 4918) and rate-limit headers (RFC 6585) added codes beyond the core set. When a client receives an unrecognised code, the rule is to treat it as the generic x00 of its class.
Why the Right Code Matters
Semantically correct codes help search engines index accurately (301 passes link equity; 410 removes pages faster than 404), allow API clients to implement correct retry logic (429 + Retry-After, 503 + Retry-After), and let monitoring systems distinguish bugs (500) from load issues (503) from auth failures (401/403).
Looking up a different status code? The full reference covers all HTTP codes with causes, fix guides, and copyable code examples for Node.js and Python.
Browse the full HTTP Status Code reference →