Re: http 1.0 keep-alive and mod

most live apache configs do the right thing to fudge keep-alive in http 1.0 if possible, but sometimes it's not possible depending on some intricate factors.
and sometimes the overarching factor is that a CGI program automatically sends some headers (clues) to the web server or even the browser clues in on the content being CGI/dynamic and does certain things..ending up in connection closing.
i'd investigate the http1.0 kruft in apache docs, and maybe even try setting a multi-part header at the start in your perl script.

the hardest line to type correctly is: stty erase ^H

Comment on Re: http 1.0 keep-alive and mod_perl

Replies are listed 'Best First'.
Re^2: http 1.0 keep-alive and mod_perl by morgon (Priest) on Oct 12, 2010 at 07:33 UTC
the overarching factor is that a CGI program automatically sends some headers (clues) to the web server This does not make any sense at all to me - could you please elaborate? try setting a multi-part header at the start in your perl script Could you please explain why this would play a role?	[reply]
Re^3: http 1.0 keep-alive and mod_perl by Khen1950fx (Canon) on Oct 12, 2010 at 15:39 UTC
Maybe this will help: Content-Length Header.	[reply]
Re^4: http 1.0 keep-alive and mod_perl by morgon (Priest) on Oct 13, 2010 at 14:37 UTC
Thanks a lot! This is indeed the difference - for static content apache sets the content-length whereas when using mod_perl you have to set it yourself. When setting a content-length header even http 1.0 clients can reuse the connection.	[reply]