[Nitro] Q about mongrel && nitro

Fang Sun nusgnaf at gmail.com
Sat Aug 5 06:41:13 EDT 2006


+1, just go for it. As George said before, the mongrel adapter is
based on webrick, after long time development mongrel is becoming
another monster to take special care.

On 8/5/06, Alexander Lazic <al-nitrogen at none.at> wrote:
> On Sam 05.08.2006 09:18, Alexander Lazic wrote:
> >
> >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?
>
> I think i have found the error but not a solution, yet.
>
> I have add this into the
> /home/al/progs/ruby/lib/ruby/gems/1.8/gems/nitro-0.31.0/lib/nitro/adapter/mongrel.rb
>
> ###   def handle(req, res)
>         .
>         .
>         after:
>
>         res.header.out << Cgi.response_headers(context)
>         res.body << context.out
>
>         puts "in MongrelAdapter at handle() after unless()"
>         puts " res.header.out.string " + res.header.out.string
>
>         puts "\n in MongrelAdapter at handle() after unless() res.body "
>         + res.body.string
> ###
>
> And have seen that no Content-Length-Header is there, now i assume that
> mongrel add this header but to late.
>
> What i also assume that the response-header should be send completely by
> mongrel.
>
> It looks to me that the mongreladapter need a little bit redesign, could
> i try it ;-)?
>
> Is anybody on this list which have more experience with ruby and mongrel
> who can help me ;-))
>
> Regards
>
> Alex
> _______________________________________________
> Nitro-general mailing list
> Nitro-general at rubyforge.org
> http://rubyforge.org/mailman/listinfo/nitro-general
>


More information about the Nitro-general mailing list