From: Jonathan Rudenberg <jonathan@titanous.com>
To: Eric Wong <normalperson@yhbt.net>
Cc: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: HEAD responses contain body
Date: Thu, 13 Jun 2013 15:28:29 -0400 [thread overview]
Message-ID: <46E5FBD0-C0EF-4338-9B78-1A8ED036A47F@titanous.com> (raw)
In-Reply-To: <20130613192145.GA11696@dcvr.yhbt.net>
On Jun 13, 2013, at 3:21 PM, Eric Wong <normalperson@yhbt.net> wrote:
> Jonathan Rudenberg <jonathan@titanous.com> wrote:
>> On Jun 13, 2013, at 2:22 PM, Eric Wong <normalperson@yhbt.net> wrote:
>>> Jonathan Rudenberg <jonathan@titanous.com> wrote:
>>>> RFC 2616 section 9.4[1] states:
>>>>
>>>>> The HEAD method is identical to GET except that the server MUST NOT return a message-body in the response.
>>>>
>>>> A HEAD request against this simple Rack app running on unicorn-4.6.2:
>>>>
>>>> require 'rack'
>>>>
>>>
>>> + use Rack::Head
>>>
>>>> run lambda { |env| [200, {}, []] }
>>>
>>> The Rack::Head middleware should be used to correctly strip HEAD
>>> responses of their bodies (frameworks such as Rails/Sinatra should
>>> already add Rack::Head to the middleware stack for you)
>>
>> This does not change the result, as the Rack::Head implementation looks like this:
>>
>> def call(env)
>> status, headers, body = @app.call(env)
>>
>> if env["REQUEST_METHOD"] == "HEAD"
>> body.close if body.respond_to? :close
>> [status, headers, []]
>> else
>> [status, headers, body]
>> end
>> end
>
> OK, I think you were hitting another problem because you were lacking
> Rack::ContentType
>
> Try the following:
> -----------------------8<---------------------
> require 'rack'
> use Rack::ContentLength # less ambiguous than Rack::Chunked adding '0'
> use Rack::Head
> use Rack::ContentType
> run lambda { |env| [200, {}, []] }
> -----------------------8<---------------------
Thanks, this stack works.
> I added the Rack::ContentLength (it's already in the default middleware
> stack) since I believe Rack::Chunked adding the '0' is a violation of
> rfc2616... I'll need to read more closely to be sure.
Hmm, so this is a bug in Rack::Chunked? My reading of the spec says that the '0' is incorrect.
_______________________________________________
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying
next prev parent reply other threads:[~2013-06-13 19:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-13 16:09 HEAD responses contain body Jonathan Rudenberg
2013-06-13 18:22 ` Eric Wong
2013-06-13 18:42 ` Jonathan Rudenberg
2013-06-13 19:21 ` Eric Wong
2013-06-13 19:28 ` Jonathan Rudenberg [this message]
2013-06-13 19:34 ` Jonathan Rudenberg
2013-06-13 19:45 ` Eric Wong
2013-06-13 19:54 ` Jonathan Rudenberg
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-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://yhbt.net/unicorn/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46E5FBD0-C0EF-4338-9B78-1A8ED036A47F@titanous.com \
--to=jonathan@titanous.com \
--cc=mongrel-unicorn@rubyforge.org \
--cc=normalperson@yhbt.net \
/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.
Code repositories for project(s) associated with this public inbox
https://yhbt.net/unicorn.git/
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).