jnunemaker / jnunemaker/httparty
OpenSSL::SSL::SSLError
Open
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 5.9k
- Forks
- 973
- Avg merge
- 1h 59m
- Merged PRs (30d)
- 1
Description
irb(main):001:0> require 'httparty'
=> true
irb(main):002:0> HTTParty.get("https://mbasic.facebook.com")
/data/data/com.termux/files/usr/lib/ruby/3.2.0/openssl/buffering.rb:214:in `sysread_nonblock': SSL_read: unexpected eof while reading (OpenSSL::SSL::SSLError)
from /data/data/com.termux/files/usr/lib/ruby/3.2.0/openssl/buffering.rb:214:in `read_nonblock'
from /data/data/com.termux/files/usr/lib/ruby/3.2.0/net/protocol.rb:218:in `rbuf_fill'
from /data/data/com.termux/files/usr/lib/ruby/3.2.0/net/protocol.rb:185:in `read_all'
from /data/data/com.termux/files/usr/lib/ruby/3.2.0/net/http/response.rb:712:in `read_all'
from /data/data/com.termux/files/usr/lib/ruby/3.2.0/net/http/response.rb:591:in `block in read_body_0'
from /data/data/com.termux/files/usr/lib/ruby/3.2.0/net/http/response.rb:550:in `inflater'
from /data/data/com.termux/files/usr/lib/ruby/3.2.0/net/http/response.rb:573:in `read_body_0'
from /data/data/com.termux/files/usr/lib/ruby/3.2.0/net/http/response.rb:344:in `read_body'
from /data/data/com.termux/files/usr/lib/ruby/3.2.0/net/http/response.rb:380:in `body'
from /data/data/com.termux/files/usr/lib/ruby/3.2.0/net/http/response.rb:302:in `reading_body'
from /data/data/com.termux/files/usr/lib/ruby/3.2.0/net/http.rb:1872:in `transport_request'
from /data/data/com.termux/files/usr/lib/ruby/3.2.0/net/http.rb:1826:in `request'
from /data/data/com.termux/files/usr/lib/ruby/3.2.0/net/http.rb:1819:in `block in request'
from /data/data/com.termux/files/usr/lib/ruby/3.2.0/net/http.rb:1238:in `start'
from /data/data/com.termux/files/usr/lib/ruby/3.2.0/net/http.rb:1817:in `request'
from /data/data/com.termux/files/usr/lib/ruby/gems/3.2.0/gems/httparty-0.21.0/lib/httparty/request.rb:156:in `perform'
... 7 levels...
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the reported HTTParty.get call in IRB and compare the failure with the stack trace through httparty-0.21.0/lib/httparty/request.rb:156 and Ruby's Net::HTTP/OpenSSL layers. Determine whether the request failure is actionable in HTTParty; done means the cause and a verified resolution or limitation are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100