308

Permanent Redirect

3xx Redirection

Back to list

Server perspective

Use 308 for permanent redirects when the redirected request must preserve the original method and body.

When to use

  • •Return 308 for durable API or route migrations where non-GET requests must keep their semantics
  • •Prefer 308 over 301 when clients should permanently update their target URI without method ambiguity

How to respond

  • •Include a Location header with the new permanent URI
  • •Keep the new target stable enough that clients can safely update stored endpoints

Headers to consider

  • •Location
  • •Cache-Control

Response body

  • •A body is optional, but the permanent target must be clear from Location

Server-side pitfalls

  • •Do not use 308 for temporary rerouting
  • •Do not choose 301 if preserving non-GET methods is part of the contract

Examples

Permanent write endpoint migration

Request:POST /api/v1/orders
Response:308 Permanent Redirect with Location: /api/v2/orders

The server provides a long-term redirect that keeps the request semantics intact.

References

Related 3xx Redirection Codes

300

Multiple Choices

There are several valid versions of this thing, and the server is asking you to pick one.

301

Moved Permanently

This moved for good. Start using the new address from now on.

302

Found

Go somewhere else for now, but don’t assume this new address is the permanent one.

303

See Other

You submitted something successfully. Now go fetch this other page to see the result.

304

Not Modified

You already have the latest version! The thing you're asking for hasn't changed since you last got it.

305

Use Proxy

This is an old HTTP idea that said, 'Use this proxy instead,' but modern systems should not rely on it.

306

Unused

This number exists in the HTTP list, but it does not mean anything you should use in a real app today.

307

Temporary Redirect

Go to this other address for now, and send the exact same kind of request there.