3083xx RedirectionLow
HTTP 308 Permanent Redirect
Defined in RFC 7538
What Does HTTP 308 Mean?
The requested resource has been permanently moved to a new URL. The client must use the same HTTP method for the redirected request.
Common Causes
- 1Permanent API endpoint migration preserving methods
- 2Domain change for API endpoints using POST/PUT
- 3Permanent URL restructure for non-GET resources
Impact
- ⚠Browser permanently redirects while preserving request method
- ⚠Bookmarks and saved URLs should be updated
Ad Space – header
Developer Fix
For web developers and application engineers
- 1Update client code to use the new URL directly
- 2Use 308 instead of 301 when POST method must be preserved
- 3Update API documentation with new endpoints
Server Admin Fix
For system administrators and DevOps engineers
- 1Configure 308 redirects for permanent URL changes on API endpoints
- 2Update DNS and server config for domain migrations
- 3Monitor for redirect chains involving 308
Ad Space – after-fix
Frequently Asked Questions
How is 308 different from 301?
Both are permanent redirects, but 308 guarantees the HTTP method won't change. With 301, a POST request might be changed to GET during the redirect. Use 308 for API endpoints that accept POST/PUT/DELETE.
Do search engines treat 308 like 301?
Most search engines treat 308 similarly to 301 for SEO purposes, passing link equity to the new URL. However, 301 has broader and more established support.
Related HTTP Status Codes
About the Author
Web Infrastructure Team
Verified against official RFC specifications and real-world server configurations. HTTP status code behavior confirmed across Apache, Nginx, and Cloudflare.