Mailing-List: contact tomcat-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <tomcat-dev@jakarta.apache.org>
Received-SPF: pass (hermes.apache.org: local policy)
Errors-To: <bsouther@fwdco.com>
Subject: Re: 5.5.4 ?
From: Ben Souther <bsouther@fwdco.com>
To: Tomcat Developers List <tomcat-dev@jakarta.apache.org>
In-Reply-To: <417D64D6.5010300@apache.org>
References: <9C5166762F311146951505C6790A9CF80229C49A@US-VS1.corp.mpi.com>
	 <417D2034.7010203@apache.org> <1098729497.17973.16.camel@bsouther>
	 <417D64D6.5010300@apache.org>
Content-Type: text/plain
Organization: F.W. Davison & Co, Inc.
Message-Id: <1098738331.17973.24.camel@bsouther>
Mime-Version: 1.0
Date: Mon, 25 Oct 2004 17:05:31 -0400
Content-Transfer-Encoding: 7bit

>Yes, I had tested it a little earlier, and it doesn't work. The path 
> would apparently have to be encoded in the same way as the URL.
OK, let me know if I can help.


> Quite 
> frankly, I'm not sure we're going to do this, since the encoding on the 
> client side is quite unpredictable.
Other than helping out and trying to learn the code, I have no interest
in seeing this one resolved.

IMHO: it's a little absurd to have to support spaces in a context path
since a browser will never send a URL with a space in it.
-Ben


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