Rainer Jung wrote:
As I started the discussion thread on releasing mod_jk 1.2.6 a few days ago, I would also prefer to have the stable code released and not adding new features. Releasing 1.2.6 as-is would already be benefitial to many people.
Henri: thank you very much for preparing the release.
For post-1.2.6 releases: JkMount only gives the ability to seperate between Apache and Tomcat on the basis of: default handled by Apache and special things handled by Tomcat.
Now often the situation is reversed: complete contexts (detected by URL-prefixes) should be handled by default by the web container, and only special static objects (subdirectorie or, file name suffixes) by apache. So JkMountExclude would make a lot of sense.
Ok just commited something for Apache 2.0 and which should be safe.
Using the env var no-jk (à la mode_deflate mod_gzip), for instance in a SetEnvIf directive, you could exclude some URL from being served by JK...
Tested on my developpment system and everything seems to works correctly.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
