HTTP 308 – Permanent Redirect
Like 301, but the method and body of the original request must be reused for the new request.
Common use case
Used for permanent API endpoint moves where the original HTTP method (e.g. PUT or DELETE) and request body must be replayed exactly against the new URL.
Example
HTTP/1.1 308 Permanent Redirect
Location: https://api.example.com/v2/orders
History
Standardised later than its siblings, in RFC 7238 (2014), to give 301's guarantees the same method-preserving fix that 307 gave 302.
Did you know?
Because it is newer, some older HTTP clients and crawlers still don't handle 308 correctly, which is why 301 remains more common for simple page redirects.