We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Now that we have a test page which is using a CA outside of our pinset (Sectigo), we need to pin it in order to trigger the interstitial page.
The text was updated successfully, but these errors were encountered:
Pin test page so that it fails as expected (fixes brave/brave-browser…
3e4f631
…#18352)
Verified PASSED using
PASSED
Steps:
https://ssl-pinning.someblog.org/
Confirmed I now see the interstitial warning page
Verification passed on
Brave | 1.32.78 Chromium: 95.0.4638.54 (Official Build) beta (64-bit) -- | -- Revision | d31a821ec901f68d0d34ccdbaea45b4c86ce543e-refs/branch-heads/4638@{#871} OS | Windows 10 Version 21H1 (Build 19043.1288)
Confirmed I now see the interstitial warning page after navigating to https://ssl-pinning.someblog.org/
https://ssl-pinning.someblog.org
1.32.x
Sorry, something went wrong.
fmarier
Successfully merging a pull request may close this issue.
Now that we have a test page which is using a CA outside of our pinset (Sectigo), we need to pin it in order to trigger the interstitial page.
The text was updated successfully, but these errors were encountered: