Issue 2170: Add AddTrust External CA Root to net/base/ev_root_ca_metadata.cc http://code.google.com/p/chromium/issues/detail?id=2170
Comment #7 by [EMAIL PROTECTED]: > ...if Chromium could build and validate certificate chains as IE7 does Wan-Teh, in a message on chromium-dev entitled "Re: Will Chrome use OCSP?", you mentioned that the "new HTTP stack" will call CertGetCertificateChain() rather than use "the WinHTTP library", but that that "new HTTP stack" is "not used by default". I think it's possible that these two HTTP stacks may trigger some different certificate path processing behaviour. When will the "new HTTP stack" be used by default? Is there a way that I can build Chromium with the "new HTTP stack" before it's used by default? -- 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 -~----------~----~----~----~------~----~------~--~---
