HTTP 308 Permanent Redirect

Redirection code, RFC 9110, section 15.4.9

What it means

Permanent redirect that keeps the method: the page has moved for good, and a POST stays a POST at the new address.

A real response

This is the request and the answer our test server gave when we asked it to return 308.

GET /c/308 HTTP/1.1
Host: example.com

HTTP/1.1 308 Permanent Redirect
Date: Sat, 14 Nov 2026 10:00:00 GMT
Content-Type: text/html; charset=utf-8
Location: /new-page
Content-Length: 11

<p>demo</p>

What browsers do with a POST

We sent a POST with the body hello to a test server that answered 308 and then reported what arrived at the new address. Chrome 157 sent POST. WebKit sent POST.

If you run the site

Use 308 for a permanent move where the method must not change, for example an API endpoint or a form handler that has a new address. RFC 9110 notes that 308 is younger than the others (2014), so very old software may not know it; 301 is the choice for those.

If you are a visitor

Your browser follows it by itself.

A common mistake

Using 301 for an API endpoint that receives POSTs: some clients will send a GET to the new address.

Registered in the IANA HTTP Status Code Registry as Permanent Redirect, defined in RFC 9110, section 15.4.9.

This is an independent guide. It is not connected with the IETF, IANA, any browser maker or any company named here. Meanings were checked against the RFC texts on 14 November 2026. Responses shown were recorded on 14 November 2026 from a small test server on the author's own computer.