How do I fix an HTTP 308 error?

Very old clients (and some webhook senders) don't handle 308 — if a legacy integration breaks, front it with an exact-match 301 for GETs only. Like 301, it is cached durably; verify with 307 first if there is any doubt about the target.

308 Permanent Redirect

The permanent, method-preserving redirect: 301's semantics with 307's strictness. POST stays POST, and clients should update stored URLs. The right choice for permanently moved API routes.

What usually causes it

API version/path migrations where non-GET methods matter
Framework-level canonical URL enforcement (Next.js redirects with permanent: true emit 308)

How to debug and fix it

Very old clients (and some webhook senders) don't handle 308 — if a legacy integration breaks, front it with an exact-match 301 for GETs only.
Like 301, it is cached durably; verify with 307 first if there is any doubt about the target.

Easily confused with

301Moved Permanently
307Temporary Redirect
302Found

Debugging an API? Build and inspect requests, check response headers, or read the full status-code debugging guide.