Zbatery/Rainbows keepalive problem?

Jake Douglas jakecdouglas at gmail.com
Sun Nov 28 12:26:01 EST 2010


On Sun, Nov 28, 2010 at 2:07 AM, Eric Wong <normalperson at yhbt.net> wrote:
> Jake Douglas <jakecdouglas at gmail.com> wrote:
>> After some more experimentation, it looks like the browser(s) fail to
>> close the connection after receiving the responses. Zbatery then waits
>> until the keepalive_timeout has expired, closes it, and accepts the
>> next connection. I gave the same application a try using Thin with
>> keep-alive and everything works fine. I spent a lot of time trying to
>> identify differences between the two, but the only useful thing I
>> managed to find is that the browser side never sends a FIN-ACK when
>> talking to Zbatery. For some reason, the browser doesn't think it's
>> finished. Any suggestions appreciated.
>
> A shot in the dark, but I wonder if web browsers do anything special
> with the Server: header with regard to keepalive.  Off the top of my
> head, I know Thin includes the "Server:" header in all responses while
> Rainbows! does not[1].
>
> Can you try loading the Rainbows::ServerToken middleware to add
> the Server header?
>
>  use Rainbows::ServerToken, "foo/bar"
>
> Any other differences in the headers the two servers send?
>
> [1] - from what I can tell, rfc2616 does not require the Server: token,
>      and recommends it to be configurable.
>
> --
> Eric Wong
> _______________________________________________
> Rainbows! mailing list - rainbows-talk at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rainbows-talk
> Do not quote signatures (like this one) or top post when replying
>


Adding the Server header does not change anything. The only other
difference I can see is that Rainbows! includes the Date header.
However, removing it also does not change the behavior. I am at a
complete loss now for what is causing this.


More information about the rainbows-talk mailing list