Moved Permanently

3xx Redirection

Server perspective

Use 301 for permanent redirects when moving the resource for good and method preservation is not the main concern.

•Return 301 for permanent content moves, canonicalization, and domain migrations
•Prefer 308 instead when redirected POST, PUT, or PATCH requests must keep the same method and body

•Include a Location header with the new URI
•Keep the target stable so caches, crawlers, and clients are not whipsawed by conflicting permanent redirects

•A response body is optional, but the redirect target should be clear from the Location header

Request:GET /blog/http-redirects-intro

Response:301 Moved Permanently with Location: /articles/http-redirects-intro

The server consolidates traffic onto the permanent canonical path.

There are several valid versions of this thing, and the server is asking you to pick one.

Go somewhere else for now, but don’t assume this new address is the permanent one.

You submitted something successfully. Now go fetch this other page to see the result.

You already have the latest version! The thing you're asking for hasn't changed since you last got it.

This is an old HTTP idea that said, 'Use this proxy instead,' but modern systems should not rely on it.

This number exists in the HTTP list, but it does not mean anything you should use in a real app today.

Go to this other address for now, and send the exact same kind of request there.

This moved for good, and you should keep using the same kind of request when you switch to the new address.