New issue
Advanced search Search tips

Issue 807535 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Jan 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

EV Certificate not displaying Properly due to failed revocation check

Reported by dmdakota...@gmail.com, Jan 31 2018

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36

Steps to reproduce the problem:
Steps to reproduce the problem:
1. Navigate to pki.darkmatter.ae or ca.darkmatter.ae
2. *Note the URL is not green nor does it say secure*
3. Open Developer tools --> Security
4. Certificate displays --> Certificate error
There are issues with the site's certificate chain (net::ERR_CERT_UNABLE_TO_CHECK_REVOCATION).
5. View Certificate --> displays certificate as valid

What is the expected behavior?
pki.darkmatter.ae and ca.darkmatter.ae should display Dark Matter L.L.C (AE) in the URL

What went wrong?
Grey https with an (i) next to it.

Upon further review chrome says net::ERR_CERT_UNABLE_TO_CHECK_REVOCATION)

Did this work before? No 

Chrome version: 63.0.3239.132  Channel: stable
OS Version: OS X 10.12.6
Flash Version: 

https://bugs.chromium.org/p/chromium/issues/detail?id=791869 . is the old report that "died" 

Please note we have checked the CRLs and OCSP and all are reachable 

If they are not reachable you go into safari and clear the cache and history of all time and this makes them reachable in safari and adobe, so if you clear cache and history of all time in chrome it also fixes it.
 
Components: Internals>Network>Certificate
Labels: -Type-Bug-Security -Restrict-View-SecurityTeam Type-Bug
Summary: EV Certificate not displaying Properly due to failed revocation check (was: EV Certificate not displaying Properly)
Status: Untriaged (was: Unconfirmed)
Reproduced on OS X 10.13.2 (17C205) with Chrome 66.3332.
Status: WontFix (was: Untriaged)
WontFix/WorkingAsIntended. The responder is failing when we attempt to check, and that is the expected behaviour.

Sign in to add a comment