Closed Bug 1742488 Opened 4 years ago Closed 4 years ago

Certificate issuer not updated on reload of tab

Categories

(Firefox :: Security, defect)

Firefox 94
defect

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: gaa, Unassigned, NeedInfo)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:94.0) Gecko/20100101 Firefox/94.0

Steps to reproduce:

I changed the certificate provider on an webserver but Firefox did not update the issuer information when pressing the padlock symbol and then click 'Connection Secure'

Actual results:

I have a website encrypted with DigiCert as cerificate issuer. When clicking the padlock and then 'Connection Secure' it says "Verified by: DigiCert". Then I change the certificate on the server to an certificate issued by Let's Encrypt.
To check the new certificate I do an Ctrl+F5 reload and click the padlock and then 'Connection Secure', it still says "Verified by: DigiCert". When going further into 'More Information' it is showing the correct Let's Encrypt information for the certificate.
By opening the same site in a new tab, clicking the padlock and then 'Connection Secure' it says "Verified by Let's Encrypt"

Expected results:

I would expect Firefox to change the certificate issuer information on a reload of the tab. Or at least on an Ctrl+F5 reload.

The Bugbug bot thinks this bug should belong to the 'Firefox::Security' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Component: Untriaged → Security
Summary: Certificate issuer not updatet on reload of tab → Certificate issuer not updated on reload of tab

I'm trying to reproduce this issue in order to confirm it, but I'm not sure how could I change the certificate on the server to an another certificate.
Could you please provide some steps to make it easier for me?
Thanks.

Flags: needinfo?(gaa)

Closing this as resolved: incomplete due the lack of response from the reporter. Please feel free to reopen the bug if the issue still persist even after following the steps mentioned in previous comments.

Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → INCOMPLETE
Keywords: dupeme
You need to log in before you can comment on or make changes to this bug.