ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: "naruse (Yui NARUSE)" <naruse@airemix.jp>
To: ruby-core@ruby-lang.org
Subject: [ruby-core:55912] [ruby-trunk - Bug #8590][Feedback] Second call of https.get results in timeout
Date: Wed, 10 Jul 2013 17:34:04 +0900	[thread overview]
Message-ID: <redmine.journal-40411.20130710173403@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-8590.20130701210755@ruby-lang.org


Issue #8590 has been updated by naruse (Yui NARUSE).

Status changed from Assigned to Feedback

I can't reproduce on
* ruby 2.1.0dev (2013-07-10 trunk 41892) [x86_64-freebsd9.1]
* OpenSSL 0.9.8y 5 Feb 2013

Feedback and patch is welcome
----------------------------------------
Bug #8590: Second call of https.get results in timeout
https://bugs.ruby-lang.org/issues/8590#change-40411

Author: yhara (Yutaka HARA)
Status: Feedback
Priority: Normal
Assignee: naruse (Yui NARUSE)
Category: lib
Target version: current: 2.1.0
ruby -v: ruby 2.0.0p247 (2013-06-27 revision 41674) [x86_64-darwin12.4.0]
Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN


Hi,

In the following code, second call of https.get results in an error "Connection reset by peer - SSL_connect" after timeout.

---
require "net/https"
https = Net::HTTP.new("secure.nicovideo.jp", 443)
#https = Net::HTTP.new("www.sbisec.co.jp", 443)  # same result for this server

https.use_ssl = true
https.ssl_version = 'TLSv1' 
https.start{ p https.get('/') }  #=> OK
https.start{ p https.get('/') }  #=> (Timeout)
---

Expected: prints response twice

Actual: prints response once, and raises the following error after timeout

/Users/yhara/.rbenv/versions/2.0.0-p247/lib/ruby/2.0.0/net/http.rb:918:in `connect': Connection reset by peer - SSL_connect (Errno::ECONNRESET)
        from /Users/yhara/.rbenv/versions/2.0.0-p247/lib/ruby/2.0.0/net/http.rb:918:in `block in connect'
        from /Users/yhara/.rbenv/versions/2.0.0-p247/lib/ruby/2.0.0/timeout.rb:52:in `timeout'
        from /Users/yhara/.rbenv/versions/2.0.0-p247/lib/ruby/2.0.0/net/http.rb:918:in `connect'
        from /Users/yhara/.rbenv/versions/2.0.0-p247/lib/ruby/2.0.0/net/http.rb:862:in `do_start'
        from /Users/yhara/.rbenv/versions/2.0.0-p247/lib/ruby/2.0.0/net/http.rb:851:in `start'

Is this a bug of Net::HTTP, or a problem of the server, or just I'm doing something wrong?

Thanks in advance.


-- 
http://bugs.ruby-lang.org/

  parent reply	other threads:[~2013-07-10  9:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-01 12:07 [ruby-core:55736] [ruby-trunk - Bug #8590][Open] Second call of https.get results in timeout yhara (Yutaka HARA)
2013-07-10  4:39 ` [ruby-core:55903] [ruby-trunk - Bug #8590][Assigned] " zzak (Zachary Scott)
2013-07-10  8:10 ` [ruby-core:55910] [ruby-trunk - Bug #8590] " Glass_saga (Masaki Matsushita)
2013-07-10  8:34 ` naruse (Yui NARUSE) [this message]
2013-07-10 23:51 ` [ruby-core:55938] " drbrain (Eric Hodel)
2013-07-11  8:51 ` [ruby-core:55945] " naruse (Yui NARUSE)
2014-01-30  6:17 ` [ruby-core:60300] " shibata.hiroshi
2019-08-15 19:49 ` [ruby-core:94371] [Ruby master Bug#8590] " merch-redmine

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.ruby-lang.org/en/community/mailing-lists/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=redmine.journal-40411.20130710173403@ruby-lang.org \
    --to=ruby-core@ruby-lang.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).