Since you are using WARP exclusively, you can remove the "Tomcat-Standalone" service from your server.xml file. After you restart Tomcat, it will no longer be listening for HTTP requests.
-----Original Message----- From: "B�hrle, Martin, FCI1" [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 06, 2002 12:01 PM To: '[EMAIL PROTECTED]' Subject: Access-Control for Tomcat-Webserver (Version 4.0.1) Hi List, we have built up a closed Intranet for our employees with an TOmcat (4.0.1), Apache and WARP-Connector - Configuration and Apache access-control, using the <LOCATION> - directive from Apache. Our Intranet - Content is served by a Tomcat-servlet. The only problem we have, is that you can still reach the content of the CMS-servlet under port 8080 from outside our business unit, because this port is the standard-tomcat HTTP-Server and the apache-access-control doesnt work in this case. Within the closed intranet we need this tomcat-http-server for testing, so I need an access-control feature like the <Location>-directive in apache, closing the port 8080 is not a solution so far. Does anybody know what to to? Thanks for Your help! Gruesse Martin Buehrle _________________________________________________________________________ Martin Buehrle, FCI1 EADS - European Aeronautic Defence and Space Company Postfach 1661 85705 UNTERSCHLEISSHEIM Telefax: +49 89 3179-8927 eMail: [EMAIL PROTECTED] _________________________________________________________________________ -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
