rack-devel archive mirror (unofficial) https://groups.google.com/group/rack-devel
 help / color / mirror / Atom feed
From: "Iñaki Baz Castillo" <ibc@aliax.net>
To: rack-devel@googlegroups.com
Subject: Re: How to get the request headers from "env" hash?
Date: Fri, 28 Aug 2009 02:35:44 +0200	[thread overview]
Message-ID: <200908280235.44184.ibc@aliax.net> (raw)


El Viernes, 28 de Agosto de 2009, escribió:
> env["rack.input"] contains a IO object with the request body, but I don't
> see in the above hash how to get the request headers (any header).
>
> Thanks for any help.

There is a class HeaderHash but as far as I realize by inspecting the code, 
it's just used to create the response, and not to store the request headers.

Do I miss something?

Thanks a lot.

-- 
Iñaki Baz Castillo <ibc@aliax.net>

             reply	other threads:[~2009-08-28  0:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-28  0:35 Iñaki Baz Castillo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-08-28  0:08 How to get the request headers from "env" hash? 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=200908280235.44184.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).