Comment #3 on issue 5699 by [email protected]: X509Certificate::Cache should not use a certificate's fingerprint alone as the key for its std::map. http://code.google.com/p/chromium/issues/detail?id=5699
This all sounds reasonable. The main reason X509Certificate::Cache exists is because when you view an HTTPS page, the renderer fires a ton of HTTPS connections to the same host that all use the same certificate. Wan-Teh, can you check if we get the same OSCertHandle for all of these requests? If so, then I think we should just use that as the key. -- 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 -~----------~----~----~----~------~----~------~--~---
