New issue
Advanced search Search tips

Issue 781868 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Nov 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 3
Type: Bug



Sign in to add a comment

Add a "Send test Expect-CT report" from chrome://net-internals#hsts

Project Member Reported by est...@chromium.org, Nov 6 2017

Issue description

Devs have a hard time determining if their Expect-CT report configurations are set up properly. We should add a button to chrome://net-internals#hsts to send a dummy report to a given report-uri.
 
Project Member

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

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/f2f09f6acfc74dfce06fece0245520b2c63e809a

commit f2f09f6acfc74dfce06fece0245520b2c63e809a
Author: Emily Stark <estark@google.com>
Date: Fri Nov 10 19:24:52 2017

Add a chrome://net-internals button for sending test Expect-CT reports

Expect-CT reports can be difficult for server operators to trigger and
debug. This CL adds dummy report functionality to the Expect-CT section of
chrome://net-internals#hsts, to allow site operators to trigger test reports to
a given report-uri.

Bug:  781868 
Cq-Include-Trybots: master.tryserver.chromium.linux:closure_compilation
Change-Id: I7adbd44c1cc7b4720522c02ccecc54a26ce0e30e
Reviewed-on: https://chromium-review.googlesource.com/756274
Commit-Queue: Emily Stark <estark@chromium.org>
Reviewed-by: Mustafa Emre Acer <meacer@chromium.org>
Reviewed-by: Matt Menke <mmenke@chromium.org>
Cr-Commit-Position: refs/heads/master@{#515631}
[modify] https://crrev.com/f2f09f6acfc74dfce06fece0245520b2c63e809a/chrome/browser/profiles/profile_io_data.cc
[modify] https://crrev.com/f2f09f6acfc74dfce06fece0245520b2c63e809a/chrome/browser/resources/net_internals/browser_bridge.js
[modify] https://crrev.com/f2f09f6acfc74dfce06fece0245520b2c63e809a/chrome/browser/resources/net_internals/domain_security_policy_view.html
[modify] https://crrev.com/f2f09f6acfc74dfce06fece0245520b2c63e809a/chrome/browser/resources/net_internals/domain_security_policy_view.js
[modify] https://crrev.com/f2f09f6acfc74dfce06fece0245520b2c63e809a/chrome/browser/ssl/chrome_expect_ct_reporter.cc
[modify] https://crrev.com/f2f09f6acfc74dfce06fece0245520b2c63e809a/chrome/browser/ssl/chrome_expect_ct_reporter.h
[modify] https://crrev.com/f2f09f6acfc74dfce06fece0245520b2c63e809a/chrome/browser/ssl/chrome_expect_ct_reporter_unittest.cc
[modify] https://crrev.com/f2f09f6acfc74dfce06fece0245520b2c63e809a/chrome/browser/ui/webui/net_internals/net_internals_ui.cc
[modify] https://crrev.com/f2f09f6acfc74dfce06fece0245520b2c63e809a/chrome/browser/ui/webui/net_internals/net_internals_ui_browsertest.cc
[modify] https://crrev.com/f2f09f6acfc74dfce06fece0245520b2c63e809a/chrome/test/data/webui/net_internals/domain_security_policy_view.js

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

Status: Fixed (was: Assigned)

Sign in to add a comment