John A Meinel пишет:
> A simple fix is to just create an "InvalidCertificate" error, with
> 'internal_error=False', and a fairly nice error message.
>
> The page you mentioned is for the "curl" commandline front end. For the library, usually this is more relevant:
> http://curl.haxx.se/libcurl/c/curl_easy_setopt.html
>
> And specifically:
> http://curl.haxx.se/libcurl/c/curl_easy_setopt.html#SSL
>
> This can easily go along with the earlier discussion with vila, about
> how to enable self-certified hosts. (env var, or config entry). We just
> allow for a way to not require verification for specific hosts.
Can we automatically fallback from pycurl to urllib if certificate
check failed? At least with warning to user?
Alexander
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
John A Meinel пишет: cate" error, with error=False' , and a fairly nice error message. curl.haxx. se/libcurl/ c/curl_ easy_setopt. html curl.haxx. se/libcurl/ c/curl_ easy_setopt. html#SSL
> A simple fix is to just create an "InvalidCertifi
> 'internal_
>
> The page you mentioned is for the "curl" commandline front end. For the library, usually this is more relevant:
> http://
>
> And specifically:
> http://
>
> This can easily go along with the earlier discussion with vila, about
> how to enable self-certified hosts. (env var, or config entry). We just
> allow for a way to not require verification for specific hosts.
Can we automatically fallback from pycurl to urllib if certificate
check failed? At least with warning to user?
Alexander enigmail. mozdev. org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://
iD8DBQFFvh2OzYr 338mxwCURAoyvAJ 0Q7k+/N8XtfmV9M EwzEhuY3Mg9qgCg hkAH tmLtIITWyk=
VqNqpQPzcuBR+
=njOA
-----END PGP SIGNATURE-----