You haven't configured apache to talk to tomcat.
You are free to have tomcat respond to http requests directly. just
change the port from 8080 to 80 in server.xml.
Some reasons that you want to keep apache around are better http
conformance (I'm pretty sure), faster for static files (images/html), more
standard logging, legacy code (php/.htacces/whatever).
If you want to glue apache to tomcat, you need to configure a modules
(mod_jserv or mod_jk) and configure apache to forward request to tomcat
(vi ajp12/ajp13) or use a proxy from apache to tomcat. The modules are
recommended.
There are serveral documents explaining this...
Good Luck,
Kenneth Topp
---
to unsubscribe: [EMAIL PROTECTED]
for more info: http://jakarta.apache.org/getinvolved/mail.html
On Thu, 2 Nov 2000, John Bateman wrote:
> Hi
>
> I've installed the mod_jk module into Apache, everything 'seems' to work
> fine. I've also configured a new App called "Servlets" just to test stuff.
>
> When I issue
> http://serverIP/Servlets/servlet/SampleCode
>
> The server says "404 cannot find file" and the logs claim "Cannot find file
> /path_to_this_context/Servlets/servlet/SampleCode
>
> When I issue:
> http://serverIP:8080/Servlets/servlet/SampleCode
>
> The Servlet runs fine.
>
> Why would I need to put the module 'inside' apache, if I'm required to run
> Tomcat as a process AND access my servlets on another port? Can I not just
> run it all off Tomcat standalone? I understand that Apache is more
> 'configurable' and handles static content better, but, I don't understand
> why I would add Tomcat into apache if I just access the same URL as I would
> if it was stand alone. Could I not get the same results leaving NOTHING
> extra inside Apache and referencing my Servlet files on the 8080 port (as
> tomcat stand alone)?
>
> Hope this wasn't too confusing.
>
>
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> John Bateman
> Cyber World Group Inc.
>
>
