WhereGoes

307 Temporary Redirect

3xx redirect

The resource is temporarily at another URL and the client must repeat the request with the same method and body, unlike how 302 often behaves.

Common causes

  • An API endpoint temporarily moves during a phased migration.
  • A load balancer shifts writes to a standby backend.
  • A staging or rollout switch routes POST traffic elsewhere.

How to fix it

  • Preserve the original method and body at the target.
  • Return a clear Location URL and revert the rule when the switch ends.
  • Do not rewrite internal links to the temporary target.

What it means for redirects and SEO

Preserves method and body, so an API POST redirected with 307 arrives intact at the target. Browsers do not cache it, keeping the original URL live in the index. Use it for temporary migrations where a 302 would drop the payload.

Trace a link that returns 307 →

Related codes