Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NEL report for subresource sxg header integrity mismatch #24555

Merged
merged 1 commit into from Jul 16, 2020

Conversation

@chromium-wpt-export-bot
Copy link
Collaborator

chromium-wpt-export-bot commented Jul 10, 2020

When there is a mismatch between the 'header-integrity' value of
'allowed-alt-sxg' link header of the cached main resource and the header
integrity value of the cached subresource, Chrome will send a NEL report
with "sxg.header_integrity_mismatch" type when navigating to the main
resource if NEL reporting was setup.

Bug: 1025074
Change-Id: I7c0ae0904a211e11b72bae95cfe2274eb9c5550a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2237212
Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Commit-Queue: Tsuyoshi Horo <horo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#788891}

Copy link
Collaborator

wpt-pr-bot left a comment

The review process for this patch is being conducted in the Chromium project.

@chromium-wpt-export-bot chromium-wpt-export-bot force-pushed the chromium-export-cl-2237212 branch 3 times, most recently from a519b5e to f532b74 Jul 14, 2020
When there is a mismatch between the 'header-integrity' value of
'allowed-alt-sxg' link header of the cached main resource and the header
integrity value of the cached subresource, Chrome will send a NEL report
with "sxg.header_integrity_mismatch" type when navigating to the main
resource if NEL reporting was setup.

Bug: 1025074
Change-Id: I7c0ae0904a211e11b72bae95cfe2274eb9c5550a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2237212
Reviewed-by: Kunihiko Sakamoto <ksakamoto@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Commit-Queue: Tsuyoshi Horo <horo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#788891}
@chromium-wpt-export-bot chromium-wpt-export-bot force-pushed the chromium-export-cl-2237212 branch from f532b74 to e662c53 Jul 16, 2020
@chromium-wpt-export-bot chromium-wpt-export-bot merged commit f6d1d4d into master Jul 16, 2020
18 checks passed
18 checks passed
Azure Pipelines Build #20200716.11 succeeded
Details
Azure Pipelines (./wpt test-jobs) ./wpt test-jobs succeeded
Details
Azure Pipelines (affected tests without changes: Safari Technology Preview) affected tests without changes: Safari Technology Preview succeeded
Details
Azure Pipelines (affected tests: Safari Technology Preview) affected tests: Safari Technology Preview succeeded
Details
Azure Pipelines (wpt.fyi hook: safari-preview-affected-tests) wpt.fyi hook: safari-preview-affected-tests succeeded
Details
Azure Pipelines (wpt.fyi hook: safari-preview-affected-tests-without-changes) wpt.fyi hook: safari-preview-affected-tests-without-changes succeeded
Details
download-firefox-nightly Community-TC (pull_request)
Details
lint Community-TC (pull_request)
Details
sink-task Community-TC (pull_request)
Details
staging.wpt.fyi - safari[experimental] Safari results
Details
wpt-chrome-dev-results Community-TC (pull_request)
Details
wpt-chrome-dev-results-without-changes Community-TC (pull_request)
Details
wpt-chrome-dev-stability Community-TC (pull_request)
Details
wpt-decision-task Community-TC (pull_request)
Details
wpt-firefox-nightly-results Community-TC (pull_request)
Details
wpt-firefox-nightly-results-without-changes Community-TC (pull_request)
Details
wpt-firefox-nightly-stability Community-TC (pull_request)
Details
wpt.fyi - safari[experimental] Safari results
Details
@chromium-wpt-export-bot chromium-wpt-export-bot deleted the chromium-export-cl-2237212 branch Jul 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

3 participants
You can’t perform that action at this time.