tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Short <a...@short.net>
Subject RE: mod_webapp and static content
Date Wed, 12 Jun 2002 18:58:19 GMT
So if that is the case is there any way currently to have a static and 
dynamic content all under one directory path

/www/Features
index.jsp
front.jpg
/www/Products
index.jsp
product1.html
product2.html

I guess one solution would be to make a /jsp directory and place all jsp 
content into that, then use the mod_webapp for that /jsp to direct to 
tomcat, but is there another way to divide between apache and tomcat?  
Perhaps using another connector besides mod_webapp?

Alex

> 
> >From the tomcat 4.0.2 release notes:
> 
> "Currently, mod_webapp forwards *all* requests under the specified context
> path to Tomcat for processing.  In a futher release, it will automatically
> configure itself to serve static resources from Apache *unless* the resource
> is subject to filtering, or subject to a security constraint, as defined in
> web.xml.  No extra configuration in httpd.conf will be required."
> 
> So the goal is to have Tomcat serve only JSP and servlet requests, and have
> Apache handle all the rest.  Tomcat stand-alone is not built to be a very
> efficient static content server...for smaller sites and sites with low
> bandwidth needs Tomcat stand-alone would probably be suitable for serving
> all content.  Anything bigger, with lots of images or other static content,
> etc. would be much better off using a Tomcat/Apache combo, as Apache is very
> good at serving static content, much better than Tomcat.


--
To unsubscribe, e-mail:   <mailto:tomcat-user-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-user-help@jakarta.apache.org>


Mime
View raw message