RE: cvs commit: jakarta-tomcat RELEASE-PLAN-3.3.1.txt

2002-02-05 Thread Vincent Massol
-Original Message- From: Bill Barker [mailto:[EMAIL PROTECTED]] Sent: 05 February 2002 06:44 To: Tomcat Developers List Subject: Re: cvs commit: jakarta-tomcat RELEASE-PLAN-3.3.1.txt Issue Description 1 Must be able to compile and run under JDK 1.1.8

RE: cvs commit: jakarta-tomcat RELEASE-PLAN-3.3.1.txt

2002-02-04 Thread GOMEZ Henri
+5958 Wrong mod_jk.conf for path pattern Easy enough to fix. The only question is if we want to change only ${Server}Config, or do we want to change the mod_jk behavior so that the two statements: JkMount /myApp/foobar/* ajp13 and JkMount /myApp/foobar* ajp13 are the same (i.e.

RE: cvs commit: jakarta-tomcat RELEASE-PLAN-3.3.1.txt

2002-02-04 Thread costinm
On Mon, 4 Feb 2002, Jonathan Reichhold wrote: /el-niƱo.jsp should be sent (per the w3c recommendation) as /el-nin%c3%b1o.jsp which is a UTF-8 encoded bytes sequences for any characters which aren't in the ~60 characters allowed from ASCII. The encoding used for the byte conversion is not

Re: cvs commit: jakarta-tomcat RELEASE-PLAN-3.3.1.txt

2002-02-04 Thread Bill Barker
Issue Description 1 Must be able to compile and run under JDK 1.1.8 + FIXED 2 Address Cactus failures running with Tomcat 3.3 + Tried but not 100% successful yet. From what little I've seen, I've never really understood this

Re: cvs commit: jakarta-tomcat RELEASE-PLAN-3.3.1.txt

2002-02-03 Thread costinm
On Sat, 2 Feb 2002, Bill Barker wrote: +4416 URI En/Decoding not working + (investigate and fix if feasible) My vote is for LATER, since as I understand the bug it is too late to test this well, and the fix (if not done right) has the potential to create

Re: cvs commit: jakarta-tomcat RELEASE-PLAN-3.3.1.txt

2002-02-03 Thread Bill Barker
- Original Message - From: [EMAIL PROTECTED] To: Tomcat Developers List [EMAIL PROTECTED] Sent: Sunday, February 03, 2002 10:36 PM Subject: Re: cvs commit: jakarta-tomcat RELEASE-PLAN-3.3.1.txt On Sat, 2 Feb 2002, Bill Barker wrote: +4416 URI En/Decoding not working

Re: cvs commit: jakarta-tomcat RELEASE-PLAN-3.3.1.txt

2002-02-02 Thread Bill Barker
Bugs to investigate fix or resolve/leave as LATER: +4600 Tomcat 3.3 redirect behavior differs from Tomcat 3.2 + (try to make 301 or 302 configurable) + +4416 URI En/Decoding not working + (investigate and fix if feasible) My

RE: cvs commit: jakarta-tomcat RELEASE-PLAN-3.3.1.txt

2002-01-22 Thread Larry Isaacs
am again out of tough with the status of J-T-C and what is or isn't ready. Cheers, Larry -Original Message- From: Bill Barker [mailto:[EMAIL PROTECTED]] Sent: Monday, January 21, 2002 6:13 PM To: Tomcat Developers List Subject: Re: cvs commit: jakarta-tomcat RELEASE-PLAN-3.3.1.txt

Re: cvs commit: jakarta-tomcat RELEASE-PLAN-3.3.1.txt

2002-01-21 Thread Bill Barker
Which AJP is planned to go with this? - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, January 21, 2002 1:39 PM Subject: cvs commit: jakarta-tomcat RELEASE-PLAN-3.3.1.txt larryi 02/01/21 13:39:37 Added: .RELEASE-PLAN-3.3.1.txt