From: "Iñaki Baz Castillo" <ibc@aliax.net>
To: rack-devel@googlegroups.com
Subject: Re: How to get the request headers from "env" hash? [SOLVED]
Date: Fri, 28 Aug 2009 03:05:31 +0200 [thread overview]
Message-ID: <200908280305.31938.ibc@aliax.net> (raw)
In-Reply-To: <200908280208.12951.ibc@aliax.net>
El Viernes, 28 de Agosto de 2009, Iñaki Baz Castillo escribió:
> but I don't see
> in the above hash how to get the request headers (any header).
Ok, it's done by inspecting env["HTTP_HEADER_NAME"].
:)
However, what about if a header is present more than once? AFAIK HTTP protocol
allows a header having multivalue in two ways:
1) A single header with values separated by comma.
2) Varios headers with same value and different name.
Rack sems to choose the last matching header as I've realized. Then, what
about multiple headers with same value?
Thanks.
--
Iñaki Baz Castillo <ibc@aliax.net>
next prev parent reply other threads:[~2009-08-28 3:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-28 0:08 How to get the request headers from "env" hash? Iñaki Baz Castillo
2009-08-28 1:05 ` Iñaki Baz Castillo [this message]
2009-08-28 1:09 ` How to get the request headers from "env" hash? [SOLVED] Iñaki Baz Castillo
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://groups.google.com/group/rack-devel
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200908280305.31938.ibc@aliax.net \
--to=rack-devel@googlegroups.com \
/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).