Return-Path: Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 38615 invoked from network); 12 Sep 2003 00:57:25 -0000 Received: from unknown (HELO nitrogen2.syd.ntt.net.au) (203.111.0.43) by daedalus.apache.org with SMTP; 12 Sep 2003 00:57:25 -0000 Received: from MARTINJ ([61.95.34.82]) by nitrogen2.syd.ntt.net.au (8.11.6p2/8.11.6/oxygen1/3.0) with SMTP id h8C0vWu57293 for ; Fri, 12 Sep 2003 10:57:32 +1000 (EST) Message-ID: <011801c378c8$d8ebcbf0$1c00a8c0@MARTINJ> From: "Martin Jericho" To: "Tomcat Users List" References: <010901c378c7$3c4648d0$1c00a8c0@MARTINJ> <3F6118A6.9050708@joedog.org> Subject: Re: Deployment on a specific port Date: Fri, 12 Sep 2003 10:57:31 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Thanks Tim, but I forgot to mention that both servlet have to be in the same webapp! One is my main servlet that handles user web requests, and the other is the AxisServlet for handling a SOAP interface into the same application. I want to stick the SOAP servlet onto a different port which can not be accessed from outside the firewall. What are the "extra tricks" you mentioned? ----- Original Message ----- From: "Tim Funk" To: "Tomcat Users List" Sent: Friday, September 12, 2003 10:51 AM Subject: Re: Deployment on a specific port > I think you can create 2 services and each service gets is own connector and > webapp. > > This also means that both servlets can't be in the same webapp. (Without > extra tricks) > > -Tim > > Martin Jericho wrote: > > > I would like to set up a single standalone instance of tomcat with connectors on two ports, and deploy one servlet to work only on one port and a different servlet to work only on the other port. Is this possible? > > > > If not, the only way I can get around it that I can see is to use the ServletRequest.getServerPort() method to check which port the request came in on an reject it if it was on the wrong port. I suspect however that this is not secure as the value returned by getServerPort() comes from the request header, which can easily be spoofed. Will the ServletRequest.getLocalPort() method in the proposed 2.4 spec be more secure? > > > > How are other people doing this? > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org > For additional commands, e-mail: tomcat-user-help@jakarta.apache.org > >