On Wed, 2005-09-14 at 18:52, Mark Thomas wrote:
> KEREM ERKAN wrote:
> > Tomcat is harder to configure and -sadly- it has a far worse documentation
> > than Apache (for now).
>
> I look forward to seeing your documentation patches in Bugzilla ;)
I will certainly document how to fix my problem onc
On Wed, 2005-09-14 at 14:04, Michael Lai wrote:
> KEREM ERKAN wrote:
>
> >OK, start with downloading and installing a binary version of Tomcat for
> >your OS and also download the 1.2.10 version of mod_jk. I think we should
> >handle the rest off list not to bother the list anymore.
> >
>
> Just
On Wed, 2005-09-14 at 13:50, Andrew Miehs wrote:
> We did some comparisons between running Tomcat 5.0 standalone, or TC
> 5.0 and Apache 2.0
>
> If you are ONLY delivering JSPs, we found that we could only deal
> with 50% of the requests when running combined Apache TC and mod_jk
OK, that's u
On Wed, 2005-09-14 at 13:29, Hassan Schroeder wrote:
> KEREM ERKAN wrote:
> > Apache has better directory/file restricting and handling than Tomcat
>
> better in what way? What actual *security* issue are we talking
> about -- in other words, what exploit is Tomcat susceptible to
> that Apache is
On Wed, 2005-09-14 at 13:22, KEREM ERKAN wrote:
> OK, start with downloading and installing a binary version of Tomcat for
> your OS and also download the 1.2.10 version of mod_jk. I think we should
> handle the rest off list not to bother the list anymore.
Yes, that's lot's already installed and
On Wed, 2005-09-14 at 12:19, KEREM ERKAN wrote:
> >
> > Unfortunately I have to keep the main port 80 httpd, as it's
> > serving 20Gb of other material (the entire campus web site).
> >
> > All I need is the trick to make Apache httpd hand off any
> > .jsp files to Tomcat.
> >
> As I am newly
On Wed, 2005-09-14 at 10:17, Michael Lai wrote:
> Peter Flynn wrote:
> >If Tomcat doesn't have any such webapp, where do I get one?
> >I certainly can't write one, as I'm not a Java programmer.
> >
>
> I am limited in my knowledge of tomcat but from my
[Sorry for the repost but I still don't have an answer to this one]
On Fri, 2005-09-09 at 15:50, Steve Dodge wrote:
> 1.is an apache http server directive.
Right, but it was put there by Tomcat's auto-config. What I was trying
to find out was, by "localhost" did Tomcat mean "my (Tomcat's)
On Fri, 2005-09-09 at 15:50, Steve Dodge wrote:
> 1.is an apache http server directive.
Right, but it was put there by Tomcat's auto-config. What I was trying
to find out was, by "localhost" did Tomcat mean "my (Tomcat's)
localhost" -- the server on 8080 -- or "Apache's localhost", which is
On Fri, 2005-09-09 at 06:13, Nikola Milutinovic wrote:
> Peter Flynn wrote:
>
> >I need to add JSP ability to a RHEL4 server running the
> >current Apache httpd from the Red Hat RPM.
[...]
> >Has anyone managed to serve JSP with Tomcat on a RHEL4
> >mac
On Fri, 2005-09-09 at 06:13, Nikola Milutinovic wrote:
> Peter Flynn wrote:
>
> >I need to add JSP ability to a RHEL4 server running the
> >current Apache httpd from the Red Hat RPM. Apparently the
> >httpd RPM available from Red Hat doesn't have the hooks
>
I need to add JSP ability to a RHEL4 server running the
current Apache httpd from the Red Hat RPM. Apparently the
httpd RPM available from Red Hat doesn't have the hooks
needed to allow JSP files to be passed to Tomcat (or if it
does, I can't find them).
Has anyone managed to serve JSP with Tomca
I'm running jakarta-tomcat-4.1.18 for the purpose of serving with
Cocoon, and that's working fine. But I also have a handful of users
who have small .jsp files, most of which are trivial (the files, not
the users :-)...with one exception, which calls on a custom search
bean. This was working fine u
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
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
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
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
17 matches
Mail list logo
