Rainbows! Rack HTTP server user/dev discussion
 help / color / mirror / code / Atom feed
From: Eric Wong <normalperson-rMlxZR9MS24@public.gmane.org>
To: Rainbows! list <rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org>
Subject: Re: Rainbows on Heroku Issues
Date: Thu, 7 Jun 2012 04:17:49 +0000	[thread overview]
Message-ID: <20120607041749.GA14953@dcvr.yhbt.net> (raw)
In-Reply-To: <CADtMPNGx4-Xa5o6w98DGJV96=0E-VOs=nSi8xiFUoTN64Xr_YA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Kunal Modi <kunalm-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> I am trying to run Rainbows on Heroku and I'm getting some odd errors,
> I was wondering if anyone had any explanation / idea on how to solve.
> I created a simple Rails 3.1/Ruby 1.9.3 app to test Unicorn/Rainbows
> on Heroku (just a simple endpoint that responds with simple json). The
> app worked as expected with Unicorn, but has some odd tendencies on
> Heroku when using Rainbows.
> 
> The request completely processes in Heroku, but always waits
> keepalive_timeout time before actually returning the response:

Try adding Rack::ContentLength and/or Rack::Chunked middleware.

You might be missing a Content-Length or "Transfer-Encoding: chunked"
header in the response, so the client is assuming HTTP/1.0 semantics
and waiting for the connection to close.  HTTP/1.1 requires either
Content-Length or chunked transfer-encoding to do persistent
connections.
_______________________________________________
Rainbows! mailing list - rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org
http://rubyforge.org/mailman/listinfo/rainbows-talk
Do not quote signatures (like this one) or top post when replying


      parent reply	other threads:[~2012-06-07  4:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-07  1:30 Rainbows on Heroku Issues Kunal Modi
     [not found] ` <CADtMPNGx4-Xa5o6w98DGJV96=0E-VOs=nSi8xiFUoTN64Xr_YA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-06-07  4:17   ` Eric Wong [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-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/rainbows/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120607041749.GA14953@dcvr.yhbt.net \
    --to=normalperson-rmlxzr9ms24@public.gmane.org \
    --cc=rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.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/rainbows.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).