Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Cannot pass TLSv1_1 or TLSv1_2 configuration options #137

Closed
saghaulor opened this issue Nov 10, 2014 · 0 comments
Closed

Cannot pass TLSv1_1 or TLSv1_2 configuration options #137

saghaulor opened this issue Nov 10, 2014 · 0 comments

Comments

@saghaulor
Copy link
Contributor

After reviewing the httpi code, the gem hardcodes acceptable SSL_VERSIONS. The highest version available to pass as an argument from savon is TLSv1.

It's my understanding that with curl when you specify TLSv1, it will attempt to use the best available version of TLS. I imagine curb does the same thing (though I'm not certain.)

I have opened a pull request to httpi to support introspecting into OpenSSL to figure out what supported versions are available. This should make httpi compatible with Ruby 1.9+-2.x+

#136
@saghaulor saghaulor changed the title Cannot pass TLSv1_1 or TLSv1_2 Cannot pass TLSv1_1 or TLSv1_2 configuration options Nov 10, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@rogerleite @saghaulor