HTTP 308 — Permanent Redirect
3xx Redirection
What it means
Like 301, but the method and body are preserved.
What to do about it
Use for permanent redirects of non-GET endpoints — an API that moved, for example.
Where it sits
308 belongs to the 3xx family: Further action is needed to complete the request — usually following a redirect.
HTTP/1.1 308 Permanent Redirect
Checking it yourself
# see the status code and headers only
curl -sI https://example.com/path
# follow redirects and print each hop
curl -sIL -o /dev/null -w "%{http_code} %{url_effective}\n" https://example.com/path
# JavaScript
const r = await fetch(url);
console.log(r.status, r.statusText);
How this code behaves
| Cacheable by default | Yes — per RFC 9110, this status is cacheable unless headers say otherwise. |
| Safe to retry | Not applicable. |
| Effect on search indexing | No direct effect. |
Returning 308 correctly
# nginx
return 308;
# Express
res.status(308).json({ error: 'Permanent Redirect' });
# Go
w.WriteHeader(308)
# Python (Flask)
return jsonify(error='Permanent Redirect'), 308;
Frequently asked questions
What does HTTP 308 mean?
Like 301, but the method and body are preserved.
How do I fix a 308 error?
Use for permanent redirects of non-GET endpoints — an API that moved, for example.
Is 308 a client or server problem?
Neither — it is an instruction to look somewhere else, and clients normally follow it automatically.