From: "drbrain (Eric Hodel)" <drbrain@...7.net>
Date: 2013-02-14T04:48:50+09:00
Subject: [ruby-core:52224] [ruby-trunk - Bug #7831][Assigned] Net::HTTP does not allow users to handle Content-Encoding in responses like 1.x


Issue #7831 has been updated by drbrain (Eric Hodel).

Status changed from Open to Assigned
Priority changed from Normal to Urgent

Naruse-San, I would like feedback for ruby 2.0.0 inclusion of this patch.
----------------------------------------
Bug #7831: Net::HTTP does not allow users to handle Content-Encoding in responses like 1.x
https://bugs.ruby-lang.org/issues/7831#change-36247

Author: drbrain (Eric Hodel)
Status: Assigned
Priority: Urgent
Assignee: naruse (Yui NARUSE)
Category: lib
Target version: 2.0.0
ruby -v: -


I added a feature to always add a feature to always add Accept-Encoding to HTTP requests and always decode HTTP responses with Content-Encoding.

On Ruby 1.9 and older you could handle Content-Encoding for yourself.

Now Ruby always handles Content-Encoding for you, but does not give you a good indicator that this has taken place. In mechanize this leads to an incompatibility as the Content-Length header is not updated from the original value.

This also disallows handling of bad server responses that browsers handle.

The attached patch (upcoming) addresses this by only handling Content-Decoding in a response if the user did not override the Accept-Encoding header.

Since this is an incompatibility I would like this fixed for Ruby 2.0.  Sorry I did not catch it sooner, I was too busy with RubyGems and RDoc.


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