HTTP 308 Permanent Redirect

What Does HTTP 308 Mean?

HTTP 308 Permanent Redirect works like 301 but guarantees that the request method and body will not change when following the redirect. It is the permanent equivalent of 307.

HTTP 308 was introduced in RFC 7538 to provide a permanent redirect that preserves the HTTP method. While 301 may (and often does) change POST to GET, 308 guarantees method preservation. This is important for APIs where permanent endpoint changes should not alter request semantics.

HTTP 308 is less commonly used than 301 because most permanent redirects involve web pages where the method change from POST to GET is actually desirable (e.g., after form submission to a new URL). Use 308 specifically when you need permanent redirect with method preservation.

Common Causes of 308 Permanent Redirect

The resource has permanently moved, and the request method must be preserved. Similar to 301 but guarantees method preservation for POST/PUT requests.

Used for permanent API endpoint changes where the HTTP method must not change during the redirect.

How to Fix 308 Permanent Redirect

HTTP 308 preserves the request method permanently. Ensure the Location header points to the correct permanent URL. If clients are not following the redirect properly, they may not support 308 — consider using 301 for browser-facing redirects.

Verify that all clients and crawlers support 308, as some older HTTP libraries may not handle it correctly.

Related Status Codes

🔍 Check Your IP Address

While you're here, find out your public IP address, location, and ISP details instantly.