Temporary Redirect

Overview

307 Temporary Redirect means the resource is temporarily at a different URL and the client must re-issue the request to the new URL while keeping the original method and body. A POST stays a POST, a PUT stays a PUT.

It removes the ambiguity of 302 (where some browsers switched the method to GET), and is used when a move is temporary but method preservation is required.

When it happens

• Use it to temporarily route API traffic to a backup server during an incident or maintenance while still forwarding the original POST/PUT request.
• It also fits forcing HTTPS without losing form POST data by carrying it safely to the new URL.

Request / Response example

POST /api/submit HTTP/1.1
Host: example.com
Content-Type: application/json

{"value":42}

HTTP/1.1 307 Temporary Redirect
Location: https://backup.example.com/api/submit
Content-Length: 0

(client re-sends the SAME POST with its body to the new URL)

In code

app.post('/api/submit', (req, res) => {
  // keep method + body, just change host temporarily
  res.redirect(307, 'https://backup.example.com/api/submit');
});

location = /api/submit {
    return 307 https://backup.example.com$request_uri;
}

Notes

• If you want the method changed to GET, use 303 See Other rather than 307.
• If the move is permanent, 308 Permanent Redirect is the correct choice instead of 307.
• Because the body must be re-sent, verify the redirect target can accept the same body and auth headers.

Related status codes

Related headers

Specification