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

Checking Content-Length can help detect cases where the connection is 
closed prematurely. I'm not sure how important this is in the 
application where the error was discovered, but it's well known as a 
problem in HTTP in general that premature closed connections are 
difficult to detect.

Regards,   Martin.

On 2013/06/14 19:03, naruse (Yui NARUSE) wrote:
>
> Issue #8182 has been updated by naruse (Yui NARUSE).
>
>
> Maybe I misunderstood, why is the assertion is needed?
> I feel it should be simply removed.
>
> Moreover chunked encoded response doesn't have Content-Length header.
> So it sounds nonsense.
> ----------------------------------------
> Bug #8182: XMLRPC request fails with "Wrong size. Was 31564, should be 1501"
> https://bugs.ruby-lang.org/issues/8182#change-39928
>
> Author: tsagadar (Marcel Mueller)
> Status: Assigned
> Priority: High
> Assignee: naruse (Yui NARUSE)
> Category: core
> Target version: current: 2.1.0
> ruby -v: ruby 2.0.0p0 (2013-02-24 revision 39474) [x86_64-darwin12.2.1]
> Backport:
>
>
> 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
>
>
>