Issue metadata
Sign in to add a comment
|
DevTools security panel "Not secure" summary not helpful on HTTP/403 NetError page
Reported by
bry...@gmail.com,
May 2 2017
|
||||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3087.0 Safari/537.36 Steps to reproduce the problem: 1. Visit website that has 'security' issue 2. Open dev tools, go to security tab 3. security overview just says 'page is not secure' with no good explanation of what's wrong/ What is the expected behavior? As with Stable channel 58, expect dev tools to show why there is a security problem and details on this What went wrong? Not showing why Chrome thinks the page is insecure or details to troubleshoot Did this work before? Yes 58 Chrome version: 60.0.3087.0 Channel: canary OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: I realize canary is bleeding edge, but wanted to make sure it's going to be difficult to resolve security issues if we cant see details.
,
May 2 2017
I can't reproduce this; perhaps you're encountering a net error rather than an SSL interstitial. Could you let me know what URLs you're having issues with?
,
May 3 2017
brysow@, Could you please respond on comment#2 with the URLs you're having issues to triage further. Thank you..!!
,
May 3 2017
This URL is an internal one, that i was testing for checking SHA-1 cert errors. So I can't share it, but here are the steps. Visit site that redirected to SHA-1 site from SHA-2 site See error regarding SHA-1 as expected Click continue under advanced to advance to new page Click back to site that sprayed the error In this case it is displaying a 403 error When error 403 is displayed, it seems to just say insecure in dev tools but no details as normal So it's sort of like a net error like Igar mentions, i.e. when you look at a site but you've lost network, but in this case it's if the site is giving back a 403 unauthorized error. When I revisit the same site later, when it does not generate a 403 error, I see the details. I can duplicate this in Chrome 58 as well. So Igar is kind of right, it behaves like this with a net error, but only when the site is giving a 403 error. Yesterday I did not correlate this only occurring when the site was giving back an http error code.
,
May 3 2017
Thank you for providing more feedback. Adding requester "jmukthavaram@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 4 2017
,
May 4 2017
|
|||||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||||
Comment 1 by eostroukhov@chromium.org
, May 2 2017