← back to v135 · update-http-request-headers-body-and-referrer-policy-on-cors-redirect

conformance · v135

v135 · update-http-request-headers-body-and-referrer-policy-on-cors-redirect — conformance probe

6 assertions drawn from the spec. Each is a single contract the spec text makes. Pass/fail reflects what this browser executed; blocked means the contract was not run because it needs user mediation, hardware, or another unavailable precondition. Open the page in Chrome stable / canary / Firefox / Safari to compare.

browser: spec: https://fetch.spec.whatwg.org/#http-redirect-fetch chromestatus: #5129859522887680 generated 2026-06-02T08:08:51Z by conformance-author-codex
0
pass
0
fail
0
blocked
6
total
id contract kind verdict detail
request-referrerpolicy-exposed Request.prototype.referrerPolicy is exposed so redirect processing can re-evaluate the active policy. spec ↗ script
request-redirect-mode-exposed Request.prototype.redirect exposes the redirect mode used by the HTTP redirect fetch algorithm. spec ↗ script
request-referrerpolicy-roundtrips The Request constructor preserves a supplied referrerPolicy value. spec ↗ script
post-request-keeps-body-before-redirect A POST Request with a body exposes the body before redirect processing rewrites it. spec ↗ script
response-redirect-creates-303 Response.redirect() can construct the 303 response shape that forces a redirected POST to become GET. spec ↗ script
response-redirect-creates-307 Response.redirect() can construct a 307 response, the redirect status that preserves method and body. spec ↗ script