HTTP status · 3xx — redirection
308 Permanent Redirect
308 Permanent Redirect is a permanent move that preserves the request method and body.
Key facts
| Class | 3xx — redirection |
|---|---|
| Standard | RFC 9110 §15.4.9 |
| Cacheable by default | Yes |
| Method handling | Preserved, including the body |
| Typical use | Permanently moved API endpoint |
What 308 means
The resource has moved permanently to the URI in Location, and clients must repeat the same method and body there. It combines the permanence of 301 with the method preservation of 307. Search engines treat it as a permanent redirect, like 301.
When 308 is the right choice
Use it when a POST endpoint has moved for good: a 301 could turn the POST into a GET and lose the payload. For ordinary page URLs, 301 is better understood by older clients and tooling. As with any redirect, point directly at the final URL and avoid chains.
Frequently asked questions
Is 308 the same as 301?
Both are permanent. 308 preserves the method and body; 301 may allow a POST to become a GET.
Do search engines understand 308?
Yes. It is treated as a permanent redirect for indexing purposes.