unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: Jonathan Rudenberg <jonathan@titanous.com>
Cc: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: HEAD responses contain body
Date: Thu, 13 Jun 2013 19:45:45 +0000	[thread overview]
Message-ID: <20130613194545.GA15049@dcvr.yhbt.net> (raw)
In-Reply-To: <46E5FBD0-C0EF-4338-9B78-1A8ED036A47F@titanous.com>

Jonathan Rudenberg <jonathan@titanous.com> wrote:
> On Jun 13, 2013, at 3:21 PM, Eric Wong <normalperson@yhbt.net> wrote:
> > Try the following:

<snip>

> Thanks, this stack works.

Good to know!

> > 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.

I think so, too.  Can you report this to the Rack folks?  (Or I can do it)

I've reproduced the issue with "rackup -s thin", too.
"rackup -s webrick" sets ContentLength, but that could be because
webrick was meant to work without Rack and adds its own headers.
_______________________________________________
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

  parent reply	other threads:[~2013-06-13 19:52 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
2013-06-13 19:34         ` Jonathan Rudenberg
2013-06-13 19:45         ` Eric Wong [this message]
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=20130613194545.GA15049@dcvr.yhbt.net \
    --to=normalperson@yhbt.net \
    --cc=jonathan@titanous.com \
    --cc=mongrel-unicorn@rubyforge.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.
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).