| Previous | Next |
| HTTP_STATUS_AMBIGUOUS | HTTP_STATUS_REDIRECT |
HTTP_STATUS_MOVED
Clients should update stored links when appropriate and follow the Location header. A 301 can be cached, so an accidental redirect may persist in browsers and intermediaries after a configuration change.
For non-idempotent methods, define the intended method behavior explicitly. If preserving the method and request body matters, 308 is the stricter permanent redirect status.
Caches and clients can remember a 301 redirect, so deploying it accidentally can have longer-lived effects than a temporary redirect. Verify the Location target, scheme, host, and path before publishing it. For methods other than GET or HEAD, also consider whether the client might change the method while following the redirect.
Looking for a different code? Search another status or error code.