tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Glenn Nielsen <gl...@mail.more.net>
Subject Re: FW: mod_jk 1.2 Apache 2 hook priorities
Date Sat, 03 May 2003 11:17:01 GMT
I don't think what you suggest is possible to do programmatically.
Apache would have already loaded and initialized itself for mod_jk
and its hook priorities before any of our code in mod_jk is called.

The only way to do this is to change the code and recompile.

Regards,

Glenn

NormW wrote:
> Good afternoon all.
> I've noted the discussion re 'hook priorities' for Apache/mod_jk and, in
> spite of little knowledge, thought the following:
> 
> The priority of hooks surely depends on what modules are loaded into Apache
> and the effect desired by the administrator; this suggests to me (at least)
> that where mod_jk hooks should perhaps be programmable (if possible), having
> as a default it's current priority (so that it won't break existing
> programs), but a parameter (to be named) might be added in, say,
> workers.properties, to allow the priority to be altered at startup and/or
> when running?
> This would resolve all the issues I've read so far...
> Norm
> 
> ----- Original Message -----
> From: "Mladen Turk" <mturk@inet.hr>
> To: "'Tomcat Developers List'" <tomcat-dev@jakarta.apache.org>;
> <glenn@mail.more.net>
> Sent: Friday, May 02, 2003 4:22 AM
> Subject: RE: FW: mod_jk 1.2 Apache 2 hook priorities
> 
> 
> 
>>>From: Glenn Nielsen
>>>
>>>Thanks for the explanation below about how it could impact
>>>use of index.jsp as a DirectoryIndex.  I will not commit the
>>>change at this time.  This will require some more thought on
>>>how to get the Alias config to work with mod_jk.
>>>
>>
>>Actually I've tested all that using HOOK_MIDDLE, and it works (didn't
>>for 2.0.39).
>>
>>I've made a patch few months ago that used HOOK_MIDDLE (for jk2), but it
>>didn't worked.
>>The explanation I gave was why it was reverted.
>>The Apache API says: "Modules that don't care when they are run should
>>use HOOK_MIDDLE".
>>
>>The question is are we really 'care'. This will need more tests, so IMO
>>it should go to
>>1.2.4-dev.
>>
>>
>>MT.
>>
>>
>>>>The problem was with internal redirects, not serving jsp
>>>
>>>files in the
>>>
>>>>Apache directory tree. Look at the mod_proxy and
>>>
>>>mod_rewrite. They all
>>>
>>>>use the HOOK_FIRST for the same reason as we
>>>>do. Since we are not dealing with the file system, the
>>>
>>>famous file_walk
>>>
>>>>didn't run, so we need
>>>>ensure that we are run before mod_dir.
>>>>
>>>>The easiest way to check if the mod_jk (and mod_jk2) hook
>>>
>>>order change
>>>
>>>>from HOOK_FIRST to HOOK_MIDDLE would break something is to set the
>>>>DirectoryIndex to include the jsp page (look at the bug 10789).
>>>>Perhaps Apache now deals with hooks differently.
>>>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
>>
>>
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org
> 



---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message