[ruby-core:56431] [ruby-trunk - Bug #8182] XMLRPC request fails with "Wrong size. Was 31564, should be 1501"

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

Category changed from core to lib
Assignee changed from naruse (Yui NARUSE) to kou (Kouhei Sutou)
Priority changed from High to Normal
Backport set to 1.9.3: DONTNEED, 2.0.0: REQUIRED

The check should be removed as following:

diff --git a/lib/xmlrpc/client.rb b/lib/xmlrpc/client.rb
index ced3d01..6aa7c1f 100644
--- a/lib/xmlrpc/client.rb
+++ b/lib/xmlrpc/client.rb
@@ -509,8 +509,6 @@ module XMLRPC # :nodoc:
       expected = resp["Content-Length"] || "<unknown>"
       if data.nil? or data.bytesize == 0
         raise "Wrong size. Was #{data.bytesize}, should be #{expected}"
-      elsif expected != "<unknown>" and expected.to_i != data.bytesize and resp["Transfer-Encoding"
-        raise "Wrong size. Was #{data.bytesize}, should be #{expected}"
       end

       parse_set_cookies(resp.get_fields("Set-Cookie"))
----------------------------------------
Bug #8182: XMLRPC request fails with "Wrong size. Was 31564, should be 1501"
https://bugs.ruby-lang.org/issues/8182#change-40965

Author: tsagadar (Marcel Mueller)
Status: Assigned
Priority: Normal
Assignee: kou (Kouhei Sutou)
Category: lib
Target version: current: 2.1.0
ruby -v: ruby 2.0.0p0 (2013-02-24 revision 39474) [x86_64-darwin12.2.1]
Backport: 1.9.3: DONTNEED, 2.0.0: REQUIRED


Since upgrading to Ruby 2.0.0p0 we can no longer use MailChimp through the Hominid gem. Hominid relies on the Ruby XMLRPC client to access MailChimp.

Debugging the issues revealed the following problem: net/http/response.rb transparently deflates the response body, removes the "content-encoding" response header (response.rb:255), but does not adjust the "content-length" header accordingly. This makes xmlrpc/client.rb:506 raise the error, that the response body and the declared length in "content-length" does not match.

I propose a high priority for this issue for two reason:
- The problem should occur whenever Ruby XMLRPC is used to access a service that supports content encoding with "deflate", "gzip", or "x-gzip"
- I don't see a workaround to this problem that could be used



-- 
http://bugs.ruby-lang.org/
_______________________________________________
ruby-core mailing list
[e-mail]
http://lists.ruby-lang.org/cgi-bin/mailman/listinfo/ruby-core