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
I have a ruby installation on my windows machine that I can probably try to replicate the bug though I have no clue how to work with cert stores in Ruby on Windows.
The text was updated successfully, but these errors were encountered:
irb(main):001:0> require 'httparty'
=> true
irb(main):003:0> HTTParty::VERSION
=> "0.13.1"
irb(main):004:0> HTTParty.get('https://shopify.com')
OpenSSL::SSL::SSLError: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed
from C:/Ruby193/lib/ruby/1.9.1/net/http.rb:799:in `connect'
from C:/Ruby193/lib/ruby/1.9.1/net/http.rb:799:in `block in connect'
from C:/Ruby193/lib/ruby/1.9.1/timeout.rb:54:in `timeout'
from C:/Ruby193/lib/ruby/1.9.1/timeout.rb:99:in `timeout'
from C:/Ruby193/lib/ruby/1.9.1/net/http.rb:799:in `connect'
from C:/Ruby193/lib/ruby/1.9.1/net/http.rb:755:in `do_start'
from C:/Ruby193/lib/ruby/1.9.1/net/http.rb:744:in `start'
from C:/Ruby193/lib/ruby/1.9.1/net/http.rb:1284:in `request'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/httparty-0.13.1/lib/httparty/request.rb:93:in `perform'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/httparty-0.13.1/lib/httparty.rb:521:in `perform_request'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/httparty-0.13.1/lib/httparty.rb:457:in `get'
from C:/Ruby193/lib/ruby/gems/1.9.1/gems/httparty-0.13.1/lib/httparty.rb:559:in `get'
from (irb):4
from C:/Ruby193/bin/irb:12:in `<main>'
I have some windows users on the shopify theme that experiencing some SSL certificate verification issues.
Prior to the update we were on
v0.10.0
which did not validate certificate authenticity at all during the default configuration.I have a ruby installation on my windows machine that I can probably try to replicate the bug though I have no clue how to work with cert stores in Ruby on Windows.
The text was updated successfully, but these errors were encountered: