On Jan 18, 2007, at 8:14 PM, [EMAIL PROTECTED] wrote:
You are correct. Turning off keepalive fixes the problem.
(We're on a VPS so we have control of httpd.conf.)
My residual problem is that neither KeepAlive nor
MaxKeepAliveRequests is allowed in a <Location> block, so
I can't just do one of them for the scripts that use Apache2::Request.
Anyone have a way to keep KeepAlive and Apache2::Request?
Might newer versions of any of the software involved fix the problem?
Thanks much,
Craig MacKenna
www.animalhead.com
personally, I would suggest this:
forget about keepalive in modperl
don't run mod_perl on port 80. run a proxy on it -- either apache
or something lightweight like nginx
run your app on port 80xx using its own apache. have keepalive
turned off.
keepalive can be turn on in your port 80 dae,pm
serve static off the proxy, only hit up mp for dynamic content.
its not as fast as if you had keepalive on the proxied connection,
but its still considerably faster than not-proxying , and you don't
deal with any of the issues of a slow-client tying up your modperl
process
there's a section in the modperl book explaining the multi-server /
multi-apache setup in depth. its online, via google
// Jonathan Vanasco
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - -
| FindMeOn.com - The cure for Multiple Web Personality Disorder
| Web Identity Management and 3D Social Networking
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - -
| RoadSound.com - Tools For Bands, Stuff For Fans
| Collaborative Online Management And Syndication Tools
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - -
