- Home
- Tools
- Developer Tools
- HTTP Status Codes
- 308 Permanent Redirect
308 Permanent Redirect
The resource has moved for good, and the request has to be repeated at the new address with the same method and body.
- Class
- 3xx Redirection. The client has to take another step to finish the request, usually fetching a different address.
- Defined in
- RFC 9110
What it looks like
HTTP/1.1 308 Permanent Redirect Location: https://api.example.com/v2/orders
When a server sends it
For a permanent move of something that receives more than GET requests: an API on a new domain, the address a form posts to, a whole site going from http to https where POST requests have to survive the redirect.
What to do with it
Clients follow it with the same method and body, and may remember the new address as they do for a 301. The same caution applies: a wrong permanent redirect stays in browser caches.
For ordinary pages 301 and 308 do the same job. The 308 is the younger of the two, standardised in 2015, and very old clients don't know it, which is why 301 is still the usual choice for pages.
Not to be confused with
| 301 Moved Permanently | Permanent too, but a POST may be turned into a GET. |
|---|---|
| 307 Temporary Redirect | The temporary version. |
How Google treats it
Google treats a 308 like a 301: a strong signal that the new address is the one to use.
All codes are on the list of HTTP status codes, which can be searched by number and by word.