AW: Access-Control for Tomcat-Webserver (Version 4.0.1)

2002-06-06 Thread Bührle, Martin, FCI1
Hi Mark, I cannot remove the standalone-service, because I need it for testing. Due to a bug I am not able to see changes out of my CMS-Servlet via WARP-Connector and Apache immediately. I just can see it under Port 8080 / Tomcat-Standalone-Server until I restart Tomcat in the night. We will

AW: Access-Control for Tomcat-Webserver (Version 4.0.1)

2002-06-06 Thread Bührle, Martin, FCI1
. Otherwise, you may have to write a filter that examines the server port and requesting IP address. -Original Message- From: Bührle, Martin, FCI1 [mailto:[EMAIL PROTECTED]] Sent: Thursday, June 06, 2002 12:38 PM To: 'Tomcat Users List' Subject: AW: Access-Control for Tomcat

AW: Access-Control for Tomcat-Webserver (Version 4.0.1)

2002-06-06 Thread Ralph Einfeldt
Depending on how good you wan't to disable access from the outside and what the outside is (other departments, internet) there are at least the following options: - Use org.apache.catalina.valves.RemoteHostValve or org.apache.catalina.valves.RemoteAddrValve To allow/block certain Hosts/IP's.