v135 · miscellaneous

Update HTTP request headers, body, and referrer policy on CORS redirect

Update the HTTP request on CORS redirect by removing the request-body-headers and body if the method has changed, and updating the referrer policy. These request updates align with the Fetch spec and match the behavior implemented by Firefox and Safari to improve compatibility.

concepts

  1. CORS Redirect

    Live trace of a redirect — see headers, body, and referrer policy mutate.

  2. What happens to your headers on a 303

    The Fetch-spec interop use case: full header-by-header table comparing the old Chrome behaviour against the post-135 alignment for both 303 (method-change) and 307 (method-preserve) redirects.

  3. Redirect chain inspector

    Pick a method (GET/POST/PUT/DELETE) and a redirect status (301/302/303/307/308). The matrix shows what survives the hop — method, body, custom headers, Referrer-Policy — under pre-135 vs 135+ semantics.

  4. Referrer Policy Simulator

    Configure origin URL, redirect target, HTTP method, redirect status, Referrer-Policy, and body presence. See the redirect chain and a side-by-side header comparison — stripped headers in red, changed values in amber — showing exactly what Chrome 135 sends after a CORS redirect.

why it shipped

Match the spec described behavior implemented by Firefox and Safari to improve compatibility.

references