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

Issue 711105 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 3
Type: Bug



Sign in to add a comment

CSP report-only violations on redirect are not reported when they are blocked as mixed content

Project Member Reported by est...@chromium.org, Apr 13 2017

Issue description

Chrome Version: 57.0.2987.133

What steps will reproduce the problem?
(1) Visit an https page that serves the header `Content-Security-Policy-Report-Only: frame-src https:; report-uri /foo`
(2) Run the following JS in the console to insert an https iframe that redirects to http:
var i = document.createElement("iframe");
document.body.appendChild(i);
i.src="https://ask.com"

What is the expected result?
CSP violation noted in the console and a report sent to /foo.

What happens instead?
Mixed Content blocking message appears in console, but no CSP violation reports.

This looks like it violates the Fetch spec; https://fetch.spec.whatwg.org/#concept-main-fetch specifies that CSP report-only violations are sent before mixed content is checked.

 

Comment 1 by est...@chromium.org, Nov 10 2017

Labels: Hotlist-EnamelAndFriendsFixIt

Comment 2 by est...@chromium.org, Feb 18 2018

Labels: -Hotlist-EnamelAndFriendsFixIt

Sign in to add a comment