-
Notifications
You must be signed in to change notification settings - Fork 992
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pypi.org: HTTP access no longer an option #3773
Comments
Hi, @Wilfred -- can you talk about why the legacy environments in question can't upgrade their TLS support versions? Thanks. |
Based on the error, you are receiving a redirect from HTTP to HTTPS. This has been the behavior from pypi.python.org for as long as I can remember.
The root of the issue you have opened is that your client is unable to negotiate a TLSv1.2 connection to PyPI. Until April 10th, 2018 this would have succeeded. PyPI is no longer accessible to clients which do not support TLSv1.2 due to our CDN provider sunsetting support. We cannot reenable access for outdated TLS protocols. If you provide more information on your environment someone may be able to assist you in upgrading to support modern TLS protocols. |
@ewdurbin it was previously possible to access
|
@Wilfred You were not communicating with the index over HTTP, in the request log you have supplied above, The root issue here is that your client does not support TLSv1.2, and PyPI only supports TLSv1.2 or higher. Again. If you are able to provide more information about your environment (OS version, TLS implementation and version, Python version, pip version) someone may be able to help you. |
It used to be the case that http://pypi.python.org/simple was accessible without HTTPS. This was important in legacy environments that don't support the certificates offered:
pip
has a--trusted-host
option to support this use case, and has the appropriate caveats in the docs.This doesn't seem to be accessible any more for pypi.org. Could this please be restored?
The text was updated successfully, but these errors were encountered: