kriswallsmith/Buzz — pull request #53 by simensen (2012-03-13 16:16:06+00:00)
Title: Provide common API for setting "verify peer" functionality across clients.

Both Curl and stream based backends support a configuration option to validate a certificate before communicating over HTTPS. This change standardizes the behavior to *not* validate certificates by default (this is the default behavior for the stream based backend) and provides a facility to change this at runtime if needed.

BC issues: Anyone who was relying on the Curl client's default behavior of failing on invalid certificate will have no warning that they are now able to connect to a site with an invalid certificate.

Coding standards: I wasn't sure what to do with the big context arrays as this involved adding a new key. I'm pretty sure this will conflict with the proxy PR that is in the queue. I'm happy to change this to another style. :)