-
Notifications
You must be signed in to change notification settings - Fork 190
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
tls_alert internal error #160
Comments
I ran into this in the context of the issue linked above ( Using It's late here and I'll have to continue investigating this tomorrow evening :) |
In cases where no proxy is configured, first establishing a TCP connection and then upgrading the connection to TLS can cause errors on some TLS servers. This commit splits the logic in such a way that configurations without proxies (presumably the majority!) will connect directly using `ssl:connect`, whilst proxy connections will still establish a socket first and then upgrade. This fixes cmullaparthi#160.
Opened #163 with a fix for this. There are some test failures on my local machine which I haven't quite figured out, but I'm really overdue for some sleep and it'll have to wait if it fails in CI, too. |
Unpinned dependency versions can cause build issues in Nix if the package registry index snapshot contains a newer version than what is packaged in nixpkgs. See NixOS/nixpkgs#43430 for context. The versions chosen here are the most recent ones currently packaged in nixpkgs, with the exception of ibrowse which has been pinned to a version that is not affected by cmullaparthi/ibrowse#160.
Unpinned dependency versions can cause build issues in Nix if the package registry index snapshot contains a newer version than what is packaged in nixpkgs. See NixOS/nixpkgs#43430 for context. The versions chosen here are the most recent ones currently packaged in nixpkgs, with the exception of ibrowse which has been pinned to a version that is not affected by cmullaparthi/ibrowse#160.
Unpinned dependency versions can cause build issues in Nix if the package registry index snapshot contains a newer version than what is packaged in nixpkgs. See NixOS/nixpkgs#43430 for context. The versions chosen here are the most recent ones currently packaged in nixpkgs, with the exception of ibrowse which has been pinned to a version that is not affected by cmullaparthi/ibrowse#160.
I went to update ibrowse from 4.2 to 4.4 and got this difference in behaviour:
ibrowse 4.2.2
ibrowse 4.4.0
Requests for other URL work fine like e.g.
'https://google.com'
work fine on both versions.What has changed between 4.2 and 4.4 in terms of ssl handling?
Elixir 1.6.0 (compiled with OTP 20)
The text was updated successfully, but these errors were encountered: