Hi,
Looks like a RESOLVED-WONTFIX ;)
Yoav Shapira http://www.yoavshapira.com
-Original Message-
From: Ben Souther [mailto:[EMAIL PROTECTED]
Sent: Monday, October 25, 2004 5:06 PM
To: Tomcat Developers List
Subject: Re: 5.5.4 ?
Yes, I had tested it a little earlier, and it doesn't work
, Shapira, Yoav wrote:
Hi,
Looks like a RESOLVED-WONTFIX ;)
Yoav Shapira http://www.yoavshapira.com
-Original Message-
From: Ben Souther [mailto:[EMAIL PROTECTED]
Sent: Monday, October 25, 2004 5:06 PM
To: Tomcat Developers List
Subject: Re: 5.5.4 ?
Yes, I had tested it a little
Hi,
What are the plans for 5.5.4 ?
I want to resolve (either fix or invalid, whatever) Bugzilla 31090
(space in context name makes session IDs crap, 31372
(AuthenticatorBase#register method), the couple of doc items, and
possibly 31656 (make Tomcat build with Struts 1.2). This week looks
Shapira, Yoav wrote:
Hi,
What are the plans for 5.5.4 ?
I want to resolve (either fix or invalid, whatever) Bugzilla 31090
I should have fixed that one, but I'm not sure, so someone needs to test it.
(space in context name makes session IDs crap, 31372
(AuthenticatorBase#register
Hi,
(space in context name makes session IDs crap, 31372
(AuthenticatorBase#register method), the couple of doc items, and
So that there are no surprises, I'm -1 for the patch proposed in the
bug
report.
I saw your comments on this issue for another bug, and was hoping you
could post them
On Mon, 2004-10-25 at 11:48, Remy Maucherat wrote:
Shapira, Yoav wrote:
Hi,
What are the plans for 5.5.4 ?
I want to resolve (either fix or invalid, whatever) Bugzilla 31090
I should have fixed that one, but I'm not sure, so someone needs to test it.
Just tested
Ben Souther wrote:
Just tested with:
jakarta-tomcat-5-bin-20041024.tar.gz
and the problem still exists.
I can test build from the CVS head tonight and test if you think it's
different.
Yes, I had tested it a little earlier, and it doesn't work. The path
would apparently have to be encoded in the
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
