ap_add_version_component and ap_set_version

[Jim Jagielski <ji...@jaguNET.com>]

Hmmmm... Am I reading this right? Once ap_set_version is called, then
ap_add_version_component can no longer be called, right, because
version_locked is true? Well, it can be called, but it no longer
does anything...
-- 
===========================================================================
   Jim Jagielski   |||   jim@jaguNET.com   |||   http://www.jaguNET.com/
            "That's no ordinary rabbit... that's the most foul,
            cruel and bad-tempered rodent you ever laid eyes on"

Re: ap_add_version_component and ap_set_version

[Rodent of Unusual Size <Ke...@Golux.Com>]

Jim Jagielski wrote:
> 
> Hmmmm... Am I reading this right? Once ap_set_version is called, then
> ap_add_version_component can no longer be called, right, because
> version_locked is true? Well, it can be called, but it no longer
> does anything...

Correct - until the pool is cleaned up at server reconfig time.
This is to keep a misplaced call to ap_add...() from adding
more stuff to it - say, if the call were put into a per-request
module callback (or worse, a directory merger).  It's only modifiable
during the module init phase.

#ken	P-)}

Ken Coar                    <http://Web.Golux.Com/coar/>
Apache Group member         <http://www.apache.org/>
"Apache Server for Dummies" <http://Web.Golux.Com/coar/ASFD/>