On Jan 27, 2014, at 7:39 AM, Alex Clark <[email protected]> wrote: > Donald Stufft <donald <at> stufft.io> writes: > >> Most likely the issue is just that PyPI isn’t realizing >> that it’s being accessed via HTTPS. > > Can you say more about this? If that's the case, then it sounds like someone > can send you a pull request to remove the (bogus?) https check and we are > done. >
I haven’t looked into it yet simply out of a function of time. Obviously PyPI is checking if it’s being accessed via HTTPS somehow, and obviously (due to the nature of the error) it doesn’t believe it is being accessed via HTTPS. Since I know that it shouldn’t be possible to access PyPI via non HTTPS I can only deduce that however it’s determining that it’s running behind HTTPS isn’t working for one reason or another. I don’t really know more than that at the moment. > _______________________________________________ > Distutils-SIG maillist - [email protected] > https://mail.python.org/mailman/listinfo/distutils-sig ----------------- Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Distutils-SIG maillist - [email protected] https://mail.python.org/mailman/listinfo/distutils-sig
