New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 806519 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

certificate viewer not showing current certificate

Reported by legendm...@gmail.com, Jan 27 2018

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36

Example URL:

Steps to reproduce the problem:
1. load https page in chromium
2. stop HTTP server
3. change HTTPS certificate
4. restart HTTP server
5. control + F5 in Chromium, open certificate viewer

What is the expected behavior?
certificate viewer showing the new certificate

What went wrong?
certificate viewer showing the old certificate. It took minutes before certificate viewer was updated. New tab/incognito were showing the new certificate.

Did this work before? N/A 

Chrome version: 63.0.3239.132  Channel: n/a
OS Version: Ubuntu 16.04.3 LTS
Flash Version: 

server side using nginx with letsencrypt(certbox). After nginx restart, the TCP connection using the old certificate has been torn down. Chromium should reflect certificate change right away, not after a certain interval.
 
Labels: Needs-Triage-M63

Comment 2 by b...@chromium.org, Jan 29 2018

Components: -Internals>Network Internals>Network>SSL
Components: -Internals>Network>SSL UI>Browser>CertificateViewer
Pretty sure this is WontFix/WorkingAsIntended.

We show the certificate used to load the resource. In the event that an item remains in the cache (whether in memory or on disk), we continue to show that certificate.
Wouldn't the new certificate be used when I did ctrl+f5?
Cc: susanjun...@techmahindra.com rsleevi@chromium.org
Labels: Triaged-ET Needs-Feedback
rsleevi@ Request you to please respond to comment #5 and also request you to confirm if this issue can be closed as WontFix.

Thanks..
Status: WontFix (was: Unconfirmed)
No, because ctrl+F5 doesn't guarantee a new network request.

Sign in to add a comment