On 12/18/06, Landry Soules <skaboss@mail.ru> wrote:
> Thanks a lot Mark and Baptiste,
>
> You were absolutely right. I had to change jk.conf this way :
>
> #For extra security, deny direct access to any WEB-INF and META-INF
> directories
> #<LocationMatch "/WEB-INF/">
> #AllowOverride None
> #Deny from all
> #</LocationMatch>
>
> #<LocationMatch "/META-INF/">
> #AllowOverride None
> #Deny from all
> #</LocationMatch>
>
> That makes Tomcat web-apps less secure, but after all that's only my
> personal server. I guess that in real-life you won't put SVN on your
> production server !
I have not worked with Tomcat in production, but when I have used
WebSphere and Apache together, the way we did it all of our web apps
always had a context root and that is how Apache knew which requests
to hand to WebSphere for processing. WebSphere already protects those
folders, so they cannot be accessed directly. I know that Tomcat does
the same, but perhaps not in this sort of setup.
Anyway, in our case, since the requests for WebSphere have one context
root, and the requests for Subversion have a different one, there is
never any issue in the requests being handled by the wrong server.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Tue Dec 19 00:37:40 2006