tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mladen Turk <>
Subject Re: Discussion mod_jk and mod_dir interaction
Date Tue, 30 Jan 2007 12:32:59 GMT
Giampaolo Tomassoni wrote:
> Finally, it seems to me that mod_jk doesn't map a request to tomcat as a sub-request,
but instead seems to tweek the req->main field, which may probably create the kind of problems
reported in BZ 36121. I'm not an expert of the apache req structure nor of the mod_jk designs,
but I have the "feeling" that it should go in a sub-request instead. Am I wrong?
> This would also allow for a probably slower, but more complete integration between Apache
and Tomcat. In example, it would be (probably?) possible to detect a 404 response from Tomcat
to a given DirectoryIndex name and attempt the next in list, if any. Which in turn could allow
a DirectoryIndex behaviour much more uniform between the mod_jk and non-mod_jk cases.

Better integration can be done by using mod_proxy_ajp that comes
with Apache 2.2.
Any other 'better' integration would probably require patching
Apache core, and thats IMHO unfeasible by majority of users.

Anything you mentioned can be done with ease using current
mod_jk and standard Apache directives, but the thing one
must always have in front, is the fact that Tomcat (or any
other backend) is part of virtual file system, not the
physical one used by Apache Httpd itself.
Static content delivery by Apache requires thorough application
design so that it can be served outside the application itself.
This is usually done by adding separate 'static' virtual directories
outside the application itself. This both ease the configuration
and increases the security, because the worst thing you can do is
to physically map the web application to the Apache Directory.
In that case all the Tomcat and Servlet spec security is jeopardized.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message