Thanks - I just want to clarify that I understand this correctly. I can
leave KeepAlive On in the main httpd.conf, and then use SetEnv nokeepalive 1
to disable it wherever I want? By the way, the docs for SetEnv say it can
be used in the main-server config or in VirtualHosts. Can I also use it on
a per-location basis? Alternatively, if I want my own special modules
(which I already use and which are relevant to this point) to set this in
the environment, at what point in the request must I set this environment
variable in order to cause Apache to disable the KeepAlive for that request?
Thanks,
Issac
PGP Key 0xE0FA561B - Fingerprint:
7E18 C018 D623 A57B 7F37 D902 8C84 7675 E0FA 561B
----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sunday, September 09, 2001 05:21
Subject: Re: KeepAlive in a Directory/Location context
>
> On Sun, 9 Sep 2001, Issac Goldstand wrote:
>
> > Hi. I was recently in a position in which I wanted to use HTTP's
> > Connection: KeepAlive on certain parts of my server, but to force a
closed
> > connection for certain URLs. As I understand it, the KeepAlive
> > configuration directive for Apache (at least for 1.3) is global for the
> > entire server. I was wondering if there was any thought of making it a
> > per-location directive so it could be changed for certain URLs... Is
there
> > any thought of doing this in Apache 1.3? 2.0?
> >
>
> This can be easily accomplished using special env variables:
> http://httpd.apache.org/docs/env.html#special
>
> Joshua.
>
