From: Hiroshi Nakamura <nakahiro@...>
Date: 2011-07-28T23:15:21+09:00
Subject: [ruby-core:38583] [Ruby 1.9 - Bug #4964] open-uri failed to handle multiple "Set-Cookie" headers


Issue #4964 has been updated by Hiroshi Nakamura.


As the original reporter said. Akr, we should use resp.to_hash instead of resp.each to avoid HTTP header concatenation.

It would introduce meta values incompatibility (String -> Array of String) so I propose to change the target version to '1.9.4'.
----------------------------------------
Bug #4964: open-uri failed to handle multiple "Set-Cookie" headers
http://redmine.ruby-lang.org/issues/4964

Author: ren li
Status: Assigned
Priority: Normal
Assignee: Akira Tanaka
Category: lib
Target version: 1.9.3
ruby -v: ruby 1.9.2p174 (2011-01-28 revision 30696) [i686-linux]


=begin
== Problem
open-uri handle multiple "Set-Cookie" headers in a wrong way. Given a header from http server like:

       Set-Cookie: name1=value1; blabla
       Set-Cookie: name2=value2; blabla


open-uri will pack it into meta info of result like:

       Set-Cookie: name1=value; blabla, name2=value2; blabla

The problem is that line 332 of open-uri.rb
        resp.each {|name,value| buf.io.meta_add_field name, value }

In turn will call invoke code in net/http.rb to join headers with ",".

== ruby -v:
ruby 1.9.2p174 (2011-01-28 revision 30696) [i686-linux]

== code:
 require 'open-uri'
 begin
   open "http://douban.fm", :redirect => false
 rescue OpenURI::HTTPRedirect => redirect
   redirect.io.meta['set-cookie']
 end




=end



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