Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 90909 invoked from network); 1 Feb 2002 08:10:26 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 1 Feb 2002 08:10:26 -0000 Received: (qmail 18263 invoked by uid 97); 1 Feb 2002 08:10:17 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@jakarta.apache.org Received: (qmail 18219 invoked by uid 97); 1 Feb 2002 08:10:16 -0000 Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Tomcat Users List" Reply-To: "Tomcat Users List" Delivered-To: mailing list tomcat-user@jakarta.apache.org Received: (qmail 18208 invoked from network); 1 Feb 2002 08:10:16 -0000 Subject: AW: why use mod_webapp? Date: Fri, 1 Feb 2002 09:09:37 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-ID: content-class: urn:content-classes:message X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0 X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: why use mod_webapp? Thread-Index: AcGqm3DgNUvkF7nUToGwV/bYTniANAAV/BlQ From: "Ralph Einfeldt" To: "Tomcat Users List" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Most points in this discussion are not true. Tomcat has not to listen on port 8080. Just define a second=20 virtual ip an use port 80 on that ip. So you wouldn't get any=20 problems with firewalls. You don't have to provide html pages to redirect. You can do it=20 with mod_alias. With that you don't need anything complicated to do the redirect. (Especially no JavaScript) Redirect /servlet RedirectMatch *.jsp /$1.jsp This is as simple as the configuration of mod_jk.=20 (With mod_webapp I'm not so familiar) The arguments I accept are: - 2 Requests instead of one. - SSL handling of apache is more efficient. - Linking between html and jsp pages is more complicated. If you want to link from a jsp to a html page you have to use=20 the domainname or the ip of the apache server in the link url. - Simpler user experience. With redirect the url in the location bar changes each time you follow a link from a html page to a jsp and vice versa. (This will not happen if you use a framed page.) - With mod_webapp you loose the aibility to define serveral setting just on the tomcat side. You have to define serveral things in apache also. - If the user disabled cookies you will loose the session each time=20 you follow a link from a html page to a jsp and vice versa. > -----Urspr=FCngliche Nachricht----- > Von: RSEQUEIRA@TRANSENTRIC.COM [mailto:RSEQUEIRA@TRANSENTRIC.COM] > Gesendet: Donnerstag, 31. Januar 2002 22:05 > An: Tomcat Users List > Betreff: Re: why use mod_webapp? > 1) First Apache can handle only static pages (and ofcourse SSI). So a > redirect would mean a client side redirect. And that is with a Refresh=3D....> or a via Javascript "window.location". The=20 2) You need to keep track of which servlet (or jsp) to redirect to. So this mean a complex html page with a lot of javascript if you plan to use a single redirect page. -- To unsubscribe: For additional commands: Troubles with the list: