HTTP topic

HTTP redirects

Redirects ask a client to continue at another location, but status-code semantics and client behavior determine what happens to the method and request content. Use this cluster to understand the model and diagnose loops, chains, and unexpected method changes.

Recommended foundation

Start here

This entry establishes the shared model used by the references, diagnostics, and experiments below.

Learn

Predict HTTP redirects and method handling

Predict a redirect by reading its status, Location value, original method, and client behavior together.

HTTP redirects

Reference

2 reviewed entries

intermediate
301 Moved Permanently
301 identifies a preferred permanent target and permits historical method rewriting for POST.
beginner
Location field
Location identifies a URI reference associated with a redirect or successful creation.

HTTP redirects

Troubleshoot

2 reviewed entries

intermediate
A redirect keeps repeating
Find the first repeated target and the layer that generated it before changing redirect rules.
intermediate
A request method changed after a redirect
Trace the redirect status and follow-up request before changing client or server behavior.

HTTP redirects

Lab

2 reviewed entries

intermediate
Compare methods across redirects
Compare historical method rewriting with explicit method-preserving redirect semantics.
intermediate
Follow a bounded redirect chain
Compare a selected bounded chain with the final URL reported after automatic following.

HTTP redirects

Start here

Predict HTTP redirects and method handling

Reference

301 Moved Permanently

Location field

Troubleshoot

A redirect keeps repeating

A request method changed after a redirect

Lab

Compare methods across redirects

Follow a bounded redirect chain