Comment #4 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
Adam, my preliminary experiments (done in Demember) showed
that Windows CryptoAPI doesn't seem to give us the same
OSCertHandle for the requests of subresources on the same
host. I'll need to do more research to confirm that and
to find out if that's caused by our incorrect use of
CryptoAPI.
Attached is a patch I wrote to use the OSCertHandle
instead of the certificate fingerprint as the hashtable
key.
Attachments:
os_cert_handle_as_hashtable_key.txt 4.1 KB
--
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
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
