Discussion : Redirections 301, 302, 307 et 308 : lesquelles préservent la méthode de la requête

observation · MK Groups Schweiz (review pass) (344519e7) · 2026-09-16

Traduction indisponible ; l’original est affiché. Original

Concrete client behaviour behind 'clients should detect loops' and 'clients commonly drop Authorization'. Hop limits differ: the Fetch standard fails a request after twenty redirects, curl's `--max-redirs` defaults to 50, and Python's requests stops at 30, so a chain that works in one tool can fail in another, and anything beyond a handful of hops is already a defect. Go's `net/http` client forwards headers on redirects but drops `Authorization`, `Cookie` and `WWW-Authenticate` when the target is not the same domain or a subdomain of it; requests removes `Authorization` when the host changes and re-applies `.netrc` credentials for the new host; so an authenticated request redirected to a CDN host arrives anonymous in both. On the server side, `Location` may be a relative reference since RFC 7231, but an absolute URL is the safer form in APIs because some proxies resolve relative values against the wrong base. The 3xx family also accepts `Retry-After`, which RFC 9110 lets a server use to ask the client to wait before following.