[Nitro] Q about mongrel && nitro

Zed Shaw zedshaw at zedshaw.com
Sat Aug 5 13:35:09 EDT 2006


On Sat, 2006-08-05 at 09:18 +0200, Alexander Lazic wrote:
> On Sam 05.08.2006 01:55, Fang Sun wrote:
> 
<snip RFC part>
Yeah, I really need to write why Mongrel does this officially.  Anyway,
on to the real question...

> At the moment i don't know a client which use pipelineing, but this
> wasn't my issue ;-)
> 

Yes, exactly, but if it's in the standard some dip will start exploring
it and use it in his next piece of crap social network.

Ok, now that I got that off my chest. :-)

> What i have meant was that after the Set-Cookie-Header a futher header
> is send which is wrong!
> 
> Anybody, nitro || mongrel, sends:
> 
> ---
> "Date: Fri, 04 Aug 2006 23:00:29 GMT\r\nStatus: 200 OK\r\nContent-Type: \
> text/html\r\nSet-Cookie: nsid=376b3e39265fc699c62ab4aa3868e3e4; \
> Path=/\r\n\r\nContent-Length: 110\r\n\r\n"
> ---
> 
> The '\r\n' is the 'delimiter' for the header as RFC2616 say ;-)
> 
> My Question was now *who* send the Cookie-Header and *who* the
> Content-Length-Header?

Mongrel doesn't do cookies, so Nitro must be hacking into the
HttpResponse object and messing things up.  Get together with me on IRC
and I'll help debug it.


-- 
Zed A. Shaw
http://www.zedshaw.com/
http://mongrel.rubyforge.org/
http://www.railsmachine.com/ -- Need Mongrel support?



More information about the Nitro-general mailing list