Return-Path: Delivered-To: apmail-jakarta-tomcat-user-archive@apache.org Received: (qmail 12953 invoked from network); 28 Mar 2003 19:52:34 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 28 Mar 2003 19:52:34 -0000 Received: (qmail 23194 invoked by uid 97); 28 Mar 2003 19:54:26 -0000 Delivered-To: qmlist-jakarta-archive-tomcat-user@nagoya.betaversion.org Received: (qmail 23187 invoked from network); 28 Mar 2003 19:54:25 -0000 Received: from daedalus.apache.org (HELO apache.org) (208.185.179.12) by nagoya.betaversion.org with SMTP; 28 Mar 2003 19:54:25 -0000 Received: (qmail 11403 invoked by uid 500); 28 Mar 2003 19:52:19 -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 11392 invoked from network); 28 Mar 2003 19:52:18 -0000 Received: from namodn.com (HELO cliff.namodn.com) (63.150.15.11) by daedalus.apache.org with SMTP; 28 Mar 2003 19:52:18 -0000 Received: from robert by cliff.namodn.com with local (Exim 3.35 #1 (Debian)) id 18yzzd-0005TT-00; Fri, 28 Mar 2003 11:58:25 -0800 Date: Fri, 28 Mar 2003 11:58:24 -0800 From: Rob Helmer To: Tomcat Users List Subject: Re: server-side redirects in web.xml Message-ID: <20030328195824.GD17417@namodn.com> References: <3E84A604.9030207@ptc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3E84A604.9030207@ptc.com> User-Agent: Mutt/1.3.28i Organization: Namodn Artists - http://www.namodn.com X-OS-Type: Debian GNU/Linux 2.2 Sender: Rob Helmer X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Fri, Mar 28, 2003 at 02:44:04PM -0500, Erik Price wrote: > >>I'm sure this is a FAQ, but I can't find a good example of this - > >> > >>I would like to do a server-side redirect on a per-application > >>basis ( e.g. the web.xml ). > >> > You can always fudge it by manipulating the URL with JavaScript/frames. Thanks for the reply, but the client won't support frames or JS ( WAP ). I am looking into a simple vhosting setup using