[#71439] [Ruby trunk - Feature #11339] [PATCH] io.c: avoid kwarg parsing in C API — matz@...
Issue #11339 has been updated by Yukihiro Matsumoto.
7 messages
2015/11/11
[#71473] Re: [Ruby trunk - Feature #11339] [PATCH] io.c: avoid kwarg parsing in C API
— Eric Wong <normalperson@...>
2015/11/13
Entire series for sockets
[#71450] Ruby 2.3.0-preview1 Released — "NARUSE, Yui" <naruse@...>
Hi,
5 messages
2015/11/11
[#71617] [Ruby trunk - Feature #11664] [PATCH] introduce rb_autoload_value to replace rb_autoload — nobu@...
Issue #11664 has been updated by Nobuyoshi Nakada.
3 messages
2015/11/20
[#71721] [Ruby trunk - Feature #11741] Migrate Ruby to Git from Subversion — me@...
Issue #11741 has been updated by Jon Moss.
4 messages
2015/11/28
[ruby-core:71614] [Ruby trunk - Feature #10674] Net::HTTP retries idempotent requests once after a timeout, but its not configurable
From:
garett.shulman@...
Date:
2015-11-20 21:42:27 UTC
List:
ruby-core #71614
Issue #10674 has been updated by Garett Shulman. I can confirm this exact behavior on 2.1.7 ---------------------------------------- Feature #10674: Net::HTTP retries idempotent requests once after a timeout,= but its not configurable https://bugs.ruby-lang.org/issues/10674#change-55015 * Author: J=C3=A9r=C3=A9my Lecour * Status: Open * Priority: Normal * Assignee: Eric Hodel ---------------------------------------- Hi, I've noticed that Net::HTTP retries idempotent requests once after a time-o= ut. It seems to adhere to the RFC 2616 (http://tools.ietf.org/html/rfc2616)= , but it is not always the best thing to do. When you don't know exactly how a remote web service works, it may be wise = to retry after a time-out. But when you know that a retry won't change anything, it should be possible= to disable this automatic retry. Otherwise, the server will have to deal w= ith 2 requests (instead of 1) and the client will effectively time-out twic= e later than expected (time for the first and second time-out). Having a basic "#retry=3D" (like we have "#read_timeout=3D" or "#open_timeo= ut" would be good first step. The value could be a simple boolean, or even an integer for the maximum num= ber of retries. The "Retry" middleware in Faraday has a more comprehensive feature set with= max retries, exponential back-off, =E2=80=A6 : https://github.com/lostisla= nd/faraday/blob/master/lib/faraday/request/retry.rb --=20 https://bugs.ruby-lang.org/