From: Ricardo Amorim Date: 2011-11-25T00:54:30+09:00 Subject: [ruby-core:41289] [ruby-trunk - Feature #2567] Net::HTTP does not handle encoding correctly Issue #2567 has been updated by Ricardo Amorim. Yui NARUSE wrote: > Is such a string always ISO-8859-1 other than non US/West Europe? Yes, ISO-8859-1 always fits. I'm mainly accessing Brazilian servers so that explains. > The sentence seems to talk about fields which allow non ASCII but usually > use only ASCII. So Location is also on this context. > And the encoding for "opaque data" should be ASCII-8BIT. With some more research, I got to this: http://tools.ietf.org/html/rfc2396, topic 2.1. So, I think you are correct. When the URI is decoded into an octet stream the correct encoding is unknown and has no default. Looks like ASCII-8BIT is the best choice but certainly people WILL have issues when redirecting to non US-ASCII URL's. ---------------------------------------- Feature #2567: Net::HTTP does not handle encoding correctly http://redmine.ruby-lang.org/issues/2567 Author: Ryan Sims Status: Assigned Priority: Low Assignee: Yui NARUSE Category: lib Target version: 2.0.0 ruby -v: ruby 1.9.1p376 (2009-12-07 revision 26041) [i686-linux] =begin A string returned by an HTTP get does not have its encoding set appropriately with the charset field, nor does the content_type report the charset. Example code demonstrating incorrect behavior is below. #!/usr/bin/ruby -w # encoding: UTF-8 require 'net/http' uri = URI.parse('http://www.hearya.com/feed/') result = Net::HTTP.start(uri.host, uri.port) {|http| http.get(uri.request_uri) } p result['content-type'] # "text/xml; charset=UTF-8" <- correct p result.content_type # "text/xml" <- incorrect; truncates the charset field puts result.body.encoding # ASCII-8BIT <- incorrect encoding, should be UTF-8 =end -- http://redmine.ruby-lang.org