Mailing-List: contact tomcat-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <tomcat-user@jakarta.apache.org>
Message-ID: <2990.192.168.0.64.1076681859.squirrel@mercury.wardbrook.com>
Date: Fri, 13 Feb 2004 14:17:39 -0000 (GMT)
Subject: Re: TC 5.0.18 RequestDespatcher bug?
From: "John Sidney-Woollett" <johnsw@wardbrook.com>
To: tomcat-user@jakarta.apache.org
Reply-To: johnsw@wardbrook.com
User-Agent: SquirrelMail/1.4.2 [CVS]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Importance: Normal
References: <402CBB80.6030102@joedog.org>
In-Reply-To: <402CBB80.6030102@joedog.org>

Tim Funk said:
> Without digging, I can't say if its a bug. BUT... There is no need to
> encode the URL if the action is a RequestDispatcher.forward(). Only one
> session may be associated with the live of a single request so once the
> session is there in the request, its there no matter how many times in
> the same request you do a RequestDispatcher.forward(). Encoding the URL
> is only needed for sending redirects back to the client or for links on
> pages.

Thanks for the clarification - I'll remove the call to URLEncode for these
situations.

Might still be a bug though... ;)

John


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org