[#75687] [Ruby trunk Bug#12416] struct rb_id_table lacks mark function — shyouhei@...
Issue #12416 has been reported by Shyouhei Urabe.
3 messages
2016/05/23
[#75763] [Ruby trunk Feature#12435] Using connect_nonblock to open TCP connections in Net::HTTP#connect — mohamed.m.m.hafez@...
Issue #12435 has been reported by Mohamed Hafez.
3 messages
2016/05/28
[#75774] Errno::EAGAIN thrown by OpenSSL::SSL::SSLSocket#connect_nonblock — Mohamed Hafez <mohamed.m.m.hafez@...>
Hi all, every now and then in my production server, I'm
4 messages
2016/05/30
[#75775] Re: Errno::EAGAIN thrown by OpenSSL::SSL::SSLSocket#connect_nonblock
— Mohamed Hafez <mohamed.m.m.hafez@...>
2016/05/30
Or does MRI's OpenSSL::SSL::SSLSocket#connect_nonblock just return
[#75782] Important: Somewhat backwards-incompatible change (Fwd: [ruby-cvs:62388] duerst:r55225 (trunk): * string.c: Activate full Unicode case mapping for UTF-8) — Martin J. Dürst <duerst@...>
With the change below, I have activated full Unicode case mapping for
4 messages
2016/05/31
[ruby-core:75730] [Ruby trunk Bug#12055] `NET::HTTPResponse` is not deflating responses with custom `Content-Range` header
From:
ggcampinho@...
Date:
2016-05-26 11:48:06 UTC
List:
ruby-core #75730
Issue #12055 has been updated by Glauber Campinho. ? ---------------------------------------- Bug #12055: `NET::HTTPResponse` is not deflating responses with custom `Content-Range` header https://bugs.ruby-lang.org/issues/12055#change-58858 * Author: Glauber Campinho * Status: Open * Priority: Normal * Assignee: * ruby -v: 2.1.6, 2.2.4 * Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN, 2.3: UNKNOWN ---------------------------------------- The RFC 7233, section 4.2 describes the the possibility of using a custom `Content-Range` header and not only for bytes [[https://tools.ietf.org/html/rfc7233#section-4.2]]. Although, the `NET::HTTPResponse` considers that `Content-Range` present on the response during the inflating is in `bytes` unit. This issue is caused by this line [[https://github.com/ruby/ruby/blob/trunk/lib/net/http/response.rb#L252]]. In the patch I changed it to check if the `Content-Range` unit is `bytes` and there is a test to reproduce the error. ---Files-------------------------------- custom_content_range.patch (1.87 KB) -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>