demo · v134

Bounce Tracking on HTTP Cache

Chrome's bounce-tracking mitigations now reach into the HTTP cache. Previously a tracker could be silently visited as a bounce hop, get its cookies wiped, but keep state alive via a cached subresource fetch. v134 clears cache for bounce-tracking-suspected origins.

probing chrome.privacy / bounce tracking signals...

Try it — bounce-flow simulator

Walk the user through a typical short-stay redirect chain. Adjust how long they stay on the tracker, then choose whether v134 cache clearing is on.

step 1ASite A — link click
step 2TTracker T — silent bounce
step 3BSite B — landing
step 4A'Return to Site A later
step 5T?T loaded as subresource
click "run flow" to simulate

The code

# Conceptually: when Chrome flags an origin as a bounce tracker
# (short stay between two unrelated sites, no user interaction),
# v134 clears not just cookies and storage, but ALSO HTTP cache
# entries from that origin. The cached subresource path is no
# longer a viable cookie-survival channel.

see also