From: merch-redmine@jeremyevans.net
To: ruby-core@ruby-lang.org
Subject: [ruby-core:94362] [Ruby master Bug#6527] WEBrick::HTTPResponse.header is a hash
Date: Thu, 15 Aug 2019 01:49:38 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-80772.20190815014938.d269ed131c4697d7@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-6527.20120601221532@ruby-lang.org
Issue #6527 has been updated by jeremyevans0 (Jeremy Evans).
Status changed from Assigned to Rejected
I don't think this is a bug. `WEBrick::HTTPResponse.header` is a hash, but the values are arrays. So if a request comes in with multiple `WWW-Authenticate` headers, `header['www-authenticate']` should contain an array of all `WWW-Authenticate` header values. This appears to be true even in 1.8.7 (https://github.com/ruby/ruby/blob/ruby_1_8_7/lib/webrick/httputils.rb#L118-L145).
----------------------------------------
Bug #6527: WEBrick::HTTPResponse.header is a hash
https://bugs.ruby-lang.org/issues/6527#change-80772
* Author: fhars (Florian Hars)
* Status: Rejected
* Priority: Normal
* Assignee: nahi (Hiroshi Nakamura)
* Target version:
* ruby -v: ruby 1.9.2p290 (2011-07-09 revision 32553) [x86_64-linux]
* Backport:
----------------------------------------
This means that there can only be one header with a given name, which makes if for example impossible to implement anything but the most trivial RFC 2617 authentication schemes, most of which would require several WWW-Authenticate headers.
This does of course affect version 1.8, too.
--
https://bugs.ruby-lang.org/
prev parent reply other threads:[~2019-08-15 1:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-01 13:15 [ruby-core:45367] [ruby-trunk - Bug #6527][Open] WEBrick::HTTPResponse.header is a hash fhars (Florian Hars)
2012-06-12 17:29 ` [ruby-core:45596] [ruby-trunk - Bug #6527][Assigned] " mame (Yusuke Endoh)
2019-08-15 1:49 ` merch-redmine [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-80772.20190815014938.d269ed131c4697d7@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).