diff options
| author | palmer@chromium.org <palmer@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-04-10 20:24:36 +0000 |
|---|---|---|
| committer | palmer@chromium.org <palmer@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-04-10 20:24:36 +0000 |
| commit | 9f972ecef902aff29dbce13b54b5440145339d8a (patch) | |
| tree | f48ac83734dd5e1c53eb2f8a3f8c3e1a0f354f04 /chrome_frame | |
| parent | 3e8eb5e2aff8540f5b6f74c385063495df78a495 (diff) | |
| download | chromium_src-9f972ecef902aff29dbce13b54b5440145339d8a.zip chromium_src-9f972ecef902aff29dbce13b54b5440145339d8a.tar.gz chromium_src-9f972ecef902aff29dbce13b54b5440145339d8a.tar.bz2 | |
Don't set MODE_DEFAULT when adding HPKP header.
Leave that to the default value, or whatever value an HSTS header set.
TEST=net_unittests; after visiting https://www.mv-rechberghausen.de, query
that domain in chrome://net-internal/#hsts and expect pins AND mode STRICT.
BUG=226068
Review URL: https://chromiumcodereview.appspot.com/13483007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@193443 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome_frame')
| -rw-r--r-- | chrome_frame/test/net/fake_external_tab.cc | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/chrome_frame/test/net/fake_external_tab.cc b/chrome_frame/test/net/fake_external_tab.cc index f5bbfba..c065333 100644 --- a/chrome_frame/test/net/fake_external_tab.cc +++ b/chrome_frame/test/net/fake_external_tab.cc @@ -254,10 +254,11 @@ void FilterDisabledTests() { // These tests use HTTPS, and IE's trust store does not have the test // certs. So these tests time out waiting for user input. The - // functionality they test (HTTP Strict Transport Security) does not - // work in Chrome Frame anyway. + // functionality they test (HTTP Strict Transport Security and + // HTTP-based Public Key Pinning) does not work in Chrome Frame anyway. "URLRequestTestHTTP.ProcessSTS", "URLRequestTestHTTP.ProcessSTSOnce", + "URLRequestTestHTTP.ProcessSTSAndPKP", // These tests have been disabled as the Chrome cookie policies don't make // sense or have not been implemented for the host network stack. |