dfobox wrote: > answer is pretty simple It sounds like their setup is publishing the JSP files under the HTTP document root as well as under the Tomcat webapps directory. This often causes the issue you experienced, and presents a security risk.
If you can, I'd recommend separating out the two directories and placing them in an appropriate location. Whichever of mod_jk or mod_proxy is in use can be configured to direct the requests to the apppropriate location. E.g. /sites/your.domain.org/httpdocs /sites/your.domain.org/webapps With this setup, I would typically map all requests to Tomcat, except for /scripts, /styles, /images and this would usually ensure that there aren't any URL mapping accidents like the one you describe. p > "NOTE: If your domain name is NOT pointing to our service yet you will need > to add your domain name and your server IP in your local hosts file in order > for you to be able to access your JSP pages since otherwise the Tomcat will > not render the context for your domain. For more info on how to include your > domain/IP in your local computer's hosts file please check: > > http://en.wikipedia.org/wiki/Hosts_file"; > > I've just added a line to hosts file to substitute my domain name by ip > address --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
