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 20757 invoked from network); 3 Jun 2000 17:56:29 -0000 Received: from phobos.unica.co.uk (root@208.239.240.147) by locus.apache.org with SMTP; 3 Jun 2000 17:56:29 -0000 Received: from george (helo=localhost) by phobos.unica.co.uk with local-esmtp (Exim 3.13 #2) id 12yI9Y-0004gc-00; Sat, 03 Jun 2000 13:56:08 -0400 Date: Sat, 3 Jun 2000 13:56:08 -0400 (EDT) From: George Pearson X-Sender: george@phobos.unica.co.uk To: tomcat-user@jakarta.apache.org Subject: Re: jsp:forward bug??? In-Reply-To: <39393745.F19D2C79@eng.sun.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N On Sat, 3 Jun 2000, Craig R. McClanahan wrote: > But in this respect, Tomcat (and any > other servlet container based on 2.1 or 2.2 that supports request dispatchers) will > behave the same way -- the client's location bar will not change because the client > has no way to know what is going on. I think it *could* know, if you sent a Content-Location header in the response, indicating the URL of the returned page. I don't know which browsers might may use of this, though.