Digital Toolchest

HTTP 3xx Redirect Codes List

Get a complete, ordered reference of HTTP 3xx status codes for redirection and routing outcomes.

HTTP 3xx redirect codes(9 registered status codes)

Based on the IANA HTTP Status Code Registry for the 3xx range. Includes any registered special entries and excludes unassigned ranges.

How to use this list

Apply HTTP 3xx codes in 3 steps

Takes ~5 seconds
  1. 1
    Choose output format

    Select text for docs, JSON for constants, or HTML for form controls.

  2. 2
    Copy or download

    Use one-click copy or download the output file.

  3. 3
    Use in your workflow

    Paste into runbooks, tests, SDK docs, or monitoring rules.

Need dropdown options for 3xx handling? Use HTML <select> output.

Common use cases

  • Developers documenting expected API response classes
  • QA teams creating focused response-code test coverage
  • Platform teams standardizing logs and alert labels

Examples

3xx example code.

Input
301
Output
301 Moved Permanently

Additional code in the same class.

Input
307
Output
307 Temporary Redirect

HTML output for select menus.

Input
301 Moved Permanently
Output
<option value="301 Moved Permanently">301 Moved Permanently</option>

Reliable HTTP 3xx response reference

This list provides a focused reference of HTTP 3xx entries so teams can standardize behavior across implementation, testing, and operations.

HTTP 3xx codes all trigger a redirect, but they're not interchangeable: 301 and 308 tell browsers and search engines the move is permanent, 302 and 307 signal a temporary redirect that shouldn't overwrite cached URLs, and 304 tells a client its cached copy is still valid instead of redirecting anywhere. This list gives you the full IANA-registered 3xx range in copy-ready text, JSON, or HTML <option> format, so routing rules, CDN configs, and redirect tests reference the correct code instead of defaulting to a generic 302.

Permanent or temporary?

301/308 tell clients and search engines to update the URL for good; 302/307 mean the move is only temporary.

  • 301/308 for permanent moves
  • 302/307 for temporary redirects
  • 304 for "nothing changed, use your cache"
One click, three formats

Grab the range as plain text, a JSON array, or ready-to-paste HTML <option> tags.

  • Plain text list
  • JSON array
  • HTML <option> tags
Scoped to redirection only

No success or error codes mixed in — just the range that governs routing and caching decisions.

  • Routing rule references
  • CDN and reverse-proxy configs
  • Cache validation logic

Choosing the right redirect code

The wrong redirect code can break caching, hurt SEO rankings, or silently drop a request body.

  • Use 301 or 308 for permanent moves so browsers and search engines update bookmarks and indexes.
  • Use 302 or 307 for temporary redirects when the original URL will be valid again later.
  • Prefer 308 (or 307) over 301/302 when the redirect must preserve the original HTTP method and body, such as a POST.

Frequently asked questions

What's the real difference between 301 and 302?>
301 means the resource has permanently moved and clients should update their stored URL. 302 means the move is temporary, so the original URL should stay in use for future requests.
Why does 307 exist if 302 already redirects?>
307 guarantees the request method and body are preserved on redirect, whereas 302 has historically been reinterpreted by clients to change a POST into a GET. 307 removes that ambiguity.
Does a 304 response include a response body?>
No. A 304 tells the client its cached copy is still valid, so the server omits the body entirely and the client reuses what it already has.

Related Developer lists

Application MIME Types List | Copy-Ready Text, JSON & HTML

Copy common application/* MIME types in text, JSON, or HTML format for API content negotiation, downloads, and file validation.

Audio MIME Types List | Copy-Ready Text, JSON & HTML

Copy common audio MIME types in text, JSON, or HTML format for uploads, playback support checks, and processing pipelines.

Common MIME Types List | Copy-Ready Text, JSON & HTML

Copy a practical common MIME types list in text, JSON, or HTML format for uploads, APIs, validation, and content handling.

HTTP 2xx Success Codes List | Copy-Ready Text, JSON & HTML

Copy all HTTP 2xx success codes in text, JSON, or HTML format for API docs, tests, and monitoring workflows, ready to paste.

HTTP 4xx Error Codes List | Copy-Ready Text, JSON & HTML

Copy all HTTP 4xx client error codes in text, JSON, or HTML format for API docs, tests, and monitoring workflows.

HTTP 5xx Error Codes List | Copy-Ready Text, JSON & HTML

Copy all HTTP 5xx server error codes in text, JSON, or HTML format for API docs, tests, and monitoring workflows.

HTTP Request Methods List | Copy-Ready Text, JSON & HTML

Copy a clean http request methods list (GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS, TRACE, CONNECT) in text, JSON, or HTML for API docs and tooling.

HTTP Status Codes List | Copy-Ready Text, JSON & HTML

Copy the complete IANA-registered HTTP status codes list in text, JSON, or HTML format for APIs, docs, testing, and observability workflows.

Image MIME Types List | Copy-Ready Text, JSON & HTML

Copy common image MIME types in text, JSON, or HTML format for upload validation, image processing, and media tooling.

Video MIME Types List | Copy-Ready Text, JSON & HTML

Copy common video MIME types in text, JSON, or HTML format for upload policies, streaming workflows, and player support checks.