You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the recent upgrade of rustls in #175, the default features were correctly turned off to enable the ring cryptography provider. However, in the process, the default feature tls12 was not re-enabled. That feature adds support for TLS 1.2 connections, so at the moment using attohttpc with rustls we see a ProtocolVersion error when attempting to fetch from registry.npmjs.org. (See this CI failure)
Testing locally, it appears that re-enabling the tls12 feature solves the underlying issue.
The text was updated successfully, but these errors were encountered:
With the recent upgrade of
rustls
in #175, the default features were correctly turned off to enable thering
cryptography provider. However, in the process, the default featuretls12
was not re-enabled. That feature adds support for TLS 1.2 connections, so at the moment using attohttpc with rustls we see aProtocolVersion
error when attempting to fetch fromregistry.npmjs.org
. (See this CI failure)Testing locally, it appears that re-enabling the
tls12
feature solves the underlying issue.The text was updated successfully, but these errors were encountered: