Re: Serving files from the Apache docroot

2003-01-28 Thread Peter Flynn
John writes: There's no need to mirror content in two directories, nor is there any need to point Tomcat at Apache's content root. You can just make Apache's doc root the same as Tomcat's Context root and the issue goes away. Or, just put your JSP and servlets in Tomcat's doc root and

Re: Serving files from the Apache docroot

2003-01-28 Thread Peter Flynn
Henning wrote: I had and have the same problem - and didn't find a solution yet. A more or less good workaround I discussed with (or better was a suggestion by) Mike Bachrynowski (who is also member on the list) could be to completely mirror the apache docroot to the tomcat docroot. This in

Re: Serving files from the Apache docroot

2003-01-28 Thread Kief Morris
Peter Flynn typed the following on 11:58 28/01/2003 + There's no need to mirror content in two directories, nor is there any need to point Tomcat at Apache's content root. You can just make Apache's doc root the same as Tomcat's Context root and the issue goes away. Or, just put your JSP

Re: Serving files from the Apache docroot

2003-01-28 Thread Peter Flynn
Henning writes: that sounds interesting to me, I don't need tomcat as http on port 8080, does anyone know how the idea can be realized? I think this has been asked ad nauseam on the Cocoon list, and I think I read that it wasn't advised because Tomcat was not designed to be secure in the way

RE: Serving files from the Apache docroot

2003-01-28 Thread Turner, John
content. That's what Apache does, and that is what it was designed to do. Tomcat was designed to be a servlet container. John -Original Message- From: Peter Flynn [mailto:[EMAIL PROTECTED]] Sent: Tuesday, January 28, 2003 7:04 AM To: [EMAIL PROTECTED] Subject: Re: Serving files from

Re: Serving files from the Apache docroot

2003-01-28 Thread Holger Klawitter
I don't know how Tomcat would or would not scale as a replacement for Apache on a big site, but it would certainly be nice to have it run on port 80 as a replacement for Apache. My suggestion for the FAQ: QUESTION: How can I make Tomcat serve at port 80 instead of 8080 on a UNIX system?

RE: Serving files from the Apache docroot

2003-01-28 Thread Turner, John
-Original Message- From: Peter Flynn [mailto:[EMAIL PROTECTED]] As far as I understood the mayor cause for all this is, that jk2 developers due to performance reasons don' t want to send back requests (for images, .js, .css ...) to the apache and - what you and Mike and I want

RE: Serving files from the Apache docroot

2003-01-28 Thread Daniel Brown
for this sort of thing? Dan. -Original Message- From: Holger Klawitter [mailto:[EMAIL PROTECTED]] Sent: 28 January 2003 13:11 To: Tomcat Users List Subject: Re: Serving files from the Apache docroot I don't know how Tomcat would or would not scale as a replacement for Apache on a big

RE: Serving files from the Apache docroot

2003-01-28 Thread Turner, John
, and suitable for this sort of thing? Dan. -Original Message- From: Holger Klawitter [mailto:[EMAIL PROTECTED]] Sent: 28 January 2003 13:11 To: Tomcat Users List Subject: Re: Serving files from the Apache docroot I don't know how Tomcat would or would not scale

Serving files from the Apache docroot

2003-01-27 Thread Peter Flynn
I just brought up Tomcat in order to serve a handful of .jsp files which are in the Apache document root. Right now of course, when Apache hands off the request to Tomcat for /foo.jsp, Tomcat comes back with a 404 because it can't find the file: HTTP Status 404 - /foo.jsp type Status report

RE: Serving files from the Apache docroot

2003-01-27 Thread Turner, John
27, 2003 6:34 AM To: [EMAIL PROTECTED] Subject: Serving files from the Apache docroot I just brought up Tomcat in order to serve a handful of .jsp files which are in the Apache document root. Right now of course, when Apache hands off the request to Tomcat for /foo.jsp, Tomcat comes back

Re: Serving files from the Apache docroot

2003-01-27 Thread Henning Heil
Hi Peter, I had and have the same problem - and didn't find a solution yet. A more or less good workaround I discussed with (or better was a suggestion by) Mike Bachrynowski (who is also member on the list) could be to completely mirror the apache docroot to the tomcat docroot. This in my

RE: Serving files from the Apache docroot

2003-01-27 Thread Turner, John
Context /jsp because of URL mapping of /*.jsp) John -Original Message- From: Henning Heil [mailto:[EMAIL PROTECTED]] Sent: Monday, January 27, 2003 9:51 AM To: Tomcat Users List Subject: Re: Serving files from the Apache docroot Hi Peter, I had and have the same problem

RE: Serving files from the Apache docroot

2003-01-27 Thread Mike Bachrynowski
because in production we would only run Tomcat behind Apache2 and never as stand-alonetherefore the problem would not occur. Mike -Original Message- From: Henning Heil [mailto:[EMAIL PROTECTED]] Sent: 27 January 2003 14:51 To: Tomcat Users List Subject: Re: Serving files from

Re: Serving files from the Apache docroot

2003-01-27 Thread Henning Heil
Mike Bachrynowski wrote: [...] My IT Operations colleagues who have a more detailed knowledge of configuring Apache than I have suggest that if Tomcat is not configured as stand-alone and MIME type support on Tomcat for all except jsp, xml and xslt is removed then all should work OK. Perhaps

RE: Serving files from the Apache docroot

2003-01-27 Thread Turner, John
To: Tomcat Users List Subject: Re: Serving files from the Apache docroot Mike Bachrynowski wrote: [...] My IT Operations colleagues who have a more detailed knowledge of configuring Apache than I have suggest that if Tomcat is not configured as stand-alone and MIME type support