Able t reproduce the issue on Latest Chrome stable i.e, 61.0.3163.79 on Windows 7/10, Mac and Linux.


Note : I see similar behavior on previous stable as well i.e., 60.0.3112.113

If I recall correctly, we've always shown net errors as neutral (or at least not secure) rather than secure. I don't know if there is an open bug specifically about higher-level HTTP error codes when the rest of the connection was secure, so I'll mark this as a new feature request.


zakerinasab@: Is comment #4 associated to the wrong bug?

Tested on latest Chrome Stable #61.0.3163.79,  Canary # 63.0.3213.0 on Windows 7, Mac 10.12.6 and Ubuntu 14.04 and able to reproduce the issue.

Using the per-revision bisect providing the bisect results,
Good build: 54.0.2817.0 (409416)
Bad build: 54.0.2819.0 (409769)

You are probably looking for a change made after 409565 (known good), but no later than 409568 (first known bad).

CHANGELOG URL:
The script might not always return single CL as suspect as some perf builds might get missing due to failure.

https://chromium.googlesource.com/chromium/src/+log/1a4008ea99084ea421a29e6b3500dc61faef7eb5..8e935ed8406619b0408bddcc8dba82548b7bdf91

https://chromium.googlesource.com/chromium/src/+/d485e9156b72ea4bb4682ffbf73ea0eb248ecb6c

From the CL above, assigning the issue to the owner concerned.

@mmenke: Could you please look into the issue, pardon me if it has nothing to do with your changes and if possible please assign it to owner concerned.

Review-URL: https://codereview.chromium.org/2190463008

This is the case for all network error pages as well (i.e., it was the case for error pages well before this).  I don't understand navigation or the security information well enough to change this, regardless, and I'm not entirely sure we want to.

lgarron@: yes. The bug number was wrong. I deleted the comments.