307 Temporary Redirect

Redirection: the client has to take another step, usually following a Location header, to complete the request.

When a server should send it. For a temporary redirect where the method and body must stay the same, such as an API endpoint answering POST from another address for a while. HSTS shows up in browser developer tools as an internal 307 from http to https.

Common causes. Redirecting an API POST, or HSTS sending a browser from http to https.

What to do. Follow the Location header with the same method.

Browsers and HTTP clients. Browsers repeat the exact request, method and body included, at the new address. It is not cached by default.

Google Search. Treated like 302: a weak signal that the redirect target should be canonical. Source: Google Search Central, How HTTP status codes, and network and DNS errors affect Google Search.

Caching. Not cacheable by default (RFC 9110 section 15.1 does not list it). A cache stores it only when the response says so with Cache-Control or Expires.

HTTP/1.1 307 Temporary Redirect
Location: https://api.example.com/v2/upload

Temporary Redirect

location = /old-page {
    return 307 https://example.com/new-page;
}

Redirect 307 /old-page https://example.com/new-page

header('Location: https://example.com/new-page', true, 307);
exit;

res.writeHead(307, { Location: 'https://example.com/new-page' });
res.end();

from flask import redirect

return redirect('https://example.com/new-page', code=307)