redirect RFC 7538
HTTP 308 Permanent Redirect
Same as 301 but explicitly preserves the HTTP method — POST stays POST.
What it means
The permanent-move counterpart of 307. Where 301 has ambiguous method-handling history (some old clients change POST → GET), 308 requires the method to stay the same. Use 308 for permanent URL migration of API endpoints where method preservation matters.
When servers send it
- •Permanent URL migration of a POST/PUT endpoint
- •API version deprecation redirecting to the new endpoint
What the client does
Follows with the exact same request. Caches the redirect. Updates search-engine references.
When you see it
- •Clean API migrations
Similar codes
301 Moved Permanently redirect
The resource has permanently moved to a new URL — clients and search engines should update their references.
302 Found redirect
Resource is temporarily at a different URL — do not update bookmarks or search engine indexes.
307 Temporary Redirect redirect
Same as 302 but explicitly preserves the HTTP method — POST stays POST.
304 Not Modified redirect
The cached copy the client already has is still valid — no body sent.
← All HTTP status codes · HTTP status cheat sheet · HTTP headers reference