HTTP 308 Permanent Redirect — What It Means & How to Fix It

The HTTP 308 Permanent Redirect status code indicates the resource has permanently moved to a new URL, and the client must use the same HTTP method for the redirect. This guide covers everything you need to know about this topic, including common causes, step-by-step solutions, and answers to frequently asked questions.

Here are the key things to understand: Like 301, this is a permanent redirect, but it guarantees the HTTP method is preserved.. Search engines treat 308 similarly to 301 for indexing purposes.. The new URL is specified in the Location header.. It was introduced to provide a permanent redirect that does not change the HTTP method.. Understanding these fundamentals will help you diagnose and resolve this issue more effectively.

The most common reasons this occurs include: A resource permanently moved and the API requires method preservation.. Domain migration for an API where POST endpoints must remain POST.. Permanent URL restructuring that must preserve the original HTTP method.. Identifying the root cause is the first step toward finding the right solution.

To resolve this, follow these recommended steps: Follow the redirect to the URL in the Location header using the same HTTP method.. Update references to use the new URL permanently.. Resend the original request body if applicable.. For web pages, 301 is usually sufficient; use 308 when method preservation matters.. If these steps do not resolve the issue, consider consulting additional resources or a qualified professional.

This article is part of our HTTP Status Codes collection on Error Codes Wiki. We provide comprehensive, up-to-date information to help you find solutions quickly.