Redirect status chooser
Pick the right redirect status code — not just where the URL goes. Compare all five codes in the table below, or test chains with the redirects simulator and the HTTP status codes reference.
Recommendation
Method on follow-up
Sample response
Common mistakes
Shareable URL keeps your answers and a short Location (e.g. ?dur=perm&method=keep for 308). Everything runs in the browser.
All redirect status codes
| Code | Name | Permanent? | Method preserved? | When to use |
|---|---|---|---|---|
About this tool
Redirect responses differ in two ways that matter in production: whether the move is permanent for caches and SEO, and whether the client must replay the same HTTP method and body on the next hop.
A 301 after POST often becomes a GET and drops the body. 302 left method behavior ambiguous for years. 303, 307, and 308 exist to make POST/PUT/API behavior explicit — pick the code that matches your intent, not whichever number your framework defaults to.