Issue 3002: Allow certificate revocation checking failures
http://code.google.com/p/chromium/issues/detail?id=3002
New issue report by [EMAIL PROTECTED]:
The new HTTP stack needs to allow certificate revocation checking
failures, i.e., failures to download a CRL or connect to an OCSP
responder.
Although this has a slight security risk, this is the current
practice among browsers, and is allowed by the W3C Web Security
Context UI Guidelines, working draft 24 July 2008, Section 8.2
Certificate Status Checking Failures.
Issue attributes:
Status: Untriaged
Owner: [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
Labels: Type-Bug Pri-2 OS-Windows Area-Misc NewHTTP
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Chromium-bugs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/chromium-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---
