New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 876676 link

Starred by 1 user
Status: Available
Owner: ----
Cc:
█ mkwst@chromium.org
kinuko@chromium.org
ricea@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocking:
issue 876678



Sign in to add a comment

beacon/headers/header-referrer-unsafe-url.https.html WPT failure

Project Member Reported by y...@yoav.ws, Aug 22 
Chrome Version: 70
OS: Linux

What steps will reproduce the problem?
https://wpt.fyi/results/beacon/headers/header-referrer-unsafe-url.https.html?label=experimental

Comment 1 by y...@yoav.ws, Aug 22

Blocking: 876678

Comment 2 by yhirano@chromium.org, Aug 23

Status: Available (was: Untriaged)

Comment 3 by ricea@chromium.org, Aug 31 

Fails with mixed content check when run on w3c-test.org. Passes locally.

Comment 4 by y...@yoav.ws, Aug 31

Cc: mkwst@chromium.org
Oh, so the test is trying to make sure that the referrer is not limited when sending beacons from HTTPS to HTTP, but such beacons are now completely blocked due to mixed content?

Mike - do you know when/why mixed content blocking for beacon requests was introduced? Do you know if it's covered by spec?

If it is, we could remove this test and replace it with one that makes sure mixed content is indeed blocked. If it isn't, apparently it's web compatible, so maybe it should be.
►

Sign in to add a comment