this afternoon and anticipate building RC1
tonight.
Cheers,
Larry
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 17, 2001 1:23 AM
To: '[EMAIL PROTECTED]'
Subject: Re: Remaining Tomcat 3.3 Issues
Larry,
I tried to fix as much as possible
On Mon, 17 Sep 2001, Larry Isaacs wrote:
3. The spec doesn't address whether a the form-login-page
and form-error-page
should be excluded from the security-constraint, but it
makes sense that
it should. It might be best to postpone this.
+1 to postpone, there is a
On Mon, 17 Sep 2001, Craig R. McClanahan wrote:
If you go this way, you would definitely want to make a note someplace
that apps cannot use a security constraint with a /* pattern, because
there is no other directory in which the login and error pages can be
put.
Because /* is a legal URL
On Mon, 17 Sep 2001, Larry Isaacs wrote:
Hi Costin,
See below for my proposal for Item #2. I think this is
the only one remaining that matters for RC1 at this point.
Let me know if you think this will work.
I think we can postpone this for RC2. You are right -
syncronization in init()
Larry,
I tried to fix as much as possible, could you post an update with what
remains open for RC1 ?
On Wed, 12 Sep 2001, Larry Isaacs wrote:
1. HttpSessionFacade.setAttribute() isn't synchronized. If a second request
called setAttribute() after this request's removeAttribute() and
:
mod_jk.c[R1.9],jk_ajp13_worker.c[R1.8].
You'll have to hunt down Mike Anderson for the details. I just remember the
commits.
- Original Message -
From: Larry Isaacs [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, September 13, 2001 1:06 PM
Subject: RE: Remaining Tomcat 3.3 Issues
],jk_ajp13_worker.c[R1.8].
You'll have to hunt down Mike Anderson for the details. I
just remember the
commits.
- Original Message -
From: Larry Isaacs [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, September 13, 2001 1:06 PM
Subject: RE: Remaining Tomcat 3.3 Issues
Thanks. Do
1798 Tomcat 3.2.2b5 with Apache and ajp13 stops responding after
This one is very difficult to reproduce (I never succeed).
We need more information on configuration. May be related with
CHUNKED. I'd like to see bug reporter to test against latest TC 3.3
Did your attempts include 3.2.2
Then we need to be sure to encode r-uri in the main branch
and to change r-unparsed_uri to encode(r-uri) in the 3.2
branch. I am swamped now and will put it on a long todo
list.. if anyone beats me to it.
And don't forget to port to j-t-c which is still using
for Apache 1.3/2.0 :::
/*
7. Evaluate whether anything should be done to deal with the use of
non-thread-safe DateFormat and related classes.
The Date used in Http10 connector response, is allready
handled by stuff I commited some time ago which use a speed hack
and return allready processed date String if it was
I interpreted #111 to be the graceful restart clean-up problem that was
fixed some months ago.
- Original Message -
From: GOMEZ Henri [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, September 13, 2001 12:13 PM
Subject: RE: Remaining Tomcat 3.3 Issues
7. Evaluate whether
-Original Message-
From: GOMEZ Henri [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 13, 2001 3:14 PM
To: [EMAIL PROTECTED]
Subject: RE: Remaining Tomcat 3.3 Issues
7. Evaluate whether anything should be done to deal with the use of
non-thread-safe DateFormat and related
]
Subject: Re: Remaining Tomcat 3.3 Issues
I interpreted #111 to be the graceful restart clean-up
problem that was
fixed some months ago.
- Original Message -
From: GOMEZ Henri [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, September 13, 2001 12:13 PM
Subject: RE: Remaining
I need CRLF for building on Windows. It appears that some files
were checked in from *nix containing CR's that were not stripped
during the commit. When I checkout or update from Windows, CVS
still adds a CR in front of all LFs. The result is CRCRLF which
Dev Studio wants to fix. I'd
Another problem is to have them bundled correctly in the src
distribution, or we need 2 distributions ( win32 and *nix) or someone
will complaint , if the dist is done in win32 , *nix people
will scream
, if reversed the other :)..
In the Tomcat 3.3 releases .zip files will contain files
]
To: [EMAIL PROTECTED]
Sent: Thursday, September 13, 2001 1:06 PM
Subject: RE: Remaining Tomcat 3.3 Issues
Thanks. Do you know if just 3.3 was affected
or 3.2.x as well? If you can give me a clue as to
what was changed, I can try to determine this.
Larry
-Original Message-
From: Bill
$0.02.
- Original Message -
From: Larry Isaacs [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, September 13, 2001 12:57 PM
Subject: RE: Remaining Tomcat 3.3 Issues
-Original Message-
From: GOMEZ Henri [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 13, 2001 3
DateTool, where the hit would be minimal. Just me $0.02.
+1
Costin
- Original Message -
From: Larry Isaacs [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, September 13, 2001 12:57 PM
Subject: RE: Remaining Tomcat 3.3 Issues
-Original Message-
From: GOMEZ Henri
Larry,
Any chance of committing the attached patch before 3.3rc1. It makes
jk_nt_service maintain a list of currently installed services in the
registry. This is so the Service Manager I have written can work. I will be
submitting the Service Manager in a few hours for committing in
, September 12, 2001 11:54 AM
To: '[EMAIL PROTECTED]'
Subject: RE: Remaining Tomcat 3.3 Issues
4. Address user authentication via Ajp12 and Ajp13. Ajp12
has a test for
isTomcatAuthentication() to see if req.setRemoteUser() should
be called.
I think Ajp13 doesn't have this yet
David Oxley wrote:
Larry,
Any chance of committing the attached patch before 3.3rc1. It makes
jk_nt_service maintain a list of currently installed services in the
registry. This is so the Service Manager I have written can work. I will be
submitting the Service Manager in a few hours for
with your
assessment.
Larry
-Original Message-
From: Ignacio J. Ortega [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 12, 2001 11:54 AM
To: '[EMAIL PROTECTED]'
Subject: RE: Remaining Tomcat 3.3 Issues
4. Address user authentication via Ajp12 and Ajp13. Ajp12
has a test
As I expected (having spent enough time on encoded URLs), I can't reproduce
1483 against B2. It always finds the correct session both in stand-alone
and Ajp13.
- Original Message -
From: Larry Isaacs [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, September 12, 2001 8:31 AM
PROTECTED]]
Sent: Wednesday, September 12, 2001 12:01 PM
To: '[EMAIL PROTECTED]'
Subject: RE: Remaining Tomcat 3.3 Issues
Larry,
Any chance of committing the attached patch before 3.3rc1. It makes
jk_nt_service maintain a list of currently installed services in the
registry. This is so
: Re: Remaining Tomcat 3.3 Issues
As I expected (having spent enough time on encoded URLs), I
can't reproduce
1483 against B2. It always finds the correct session both in
stand-alone
and Ajp13.
That's true of mod_jk in j-t-c. At least through B2 the mod_jk that ships
with 3.3 uses r-uri.
- Original Message -
From: Keith Wannamaker [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, September 12, 2001 12:11 PM
Subject: RE: Remaining Tomcat 3.3 Issues
mod_jk uses (used
On Wed, Sep 12, 2001 at 03:19:15PM -0400, Larry Isaacs wrote:
One of the main aspects of this issue is for me to
become informed as to the state of Tomcat 3.3's mod_jk
with respect to this. Tomcat 3.3's mod_jk.c has:
s-req_uri = r-uri;
which, by the statement below, appears to be
| -Original Message-
| From: Larry Isaacs [mailto:[EMAIL PROTECTED]]
| Sent: Wednesday, September 12, 2001 3:19 PM
| To: '[EMAIL PROTECTED]'
| Subject: RE: Remaining Tomcat 3.3 Issues
|
|
| One of the main aspects of this issue is for me to
| become informed as to the state of Tomcat 3.3's mod_jk
Message-
From: Keith Wannamaker [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, September 12, 2001 3:11 PM
To: [EMAIL PROTECTED]
Subject: RE: Remaining Tomcat 3.3 Issues
mod_jk uses (used?) r-unparsed_uri to preserve encoding.
Therefore, any mod_rewrite munging of r-uri is invisible
]]
| Sent: Wednesday, September 12, 2001 6:10 PM
| To: '[EMAIL PROTECTED]'
| Subject: RE: Remaining Tomcat 3.3 Issues
|
|
|
| My current 'preference' is to use r-uri, as in the main branch ( and how
| it used to be ). That keeps rewrite working and is consistent with most
| apache modules.
PM
| To: '[EMAIL PROTECTED]'
| Subject: RE: Remaining Tomcat 3.3 Issues
|
|
|
| My current 'preference' is to use r-uri, as in the main branch ( and how
| it used to be ). That keeps rewrite working and is consistent with most
| apache modules.
]
Asunto: RE: Remaining Tomcat 3.3 Issues
On Wed, 12 Sep 2001, Keith Wannamaker wrote:
Then we need to be sure to encode r-uri in the main branch
and to change r-unparsed_uri to encode(r-uri) in the 3.2
branch. I am swamped now and will put it on a long todo
list.. if anyone beats me
On Thu, 13 Sep 2001, Ignacio J. Ortega wrote:
Please give me some info..
It's possible to use no cookies sessions without using mod_rewrite in
apache?
I don't know what you mean - mod_jk is taking care of decuding the
sessionId, and it support both cookie and URL decoding.
I didn't even
?
Saludos ,
Ignacio J. Ortega
-Mensaje original-
De: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Enviado el: jueves 13 de septiembre de 2001 1:16
Para: '[EMAIL PROTECTED]'
Asunto: RE: Remaining Tomcat 3.3 Issues
On Thu, 13 Sep 2001, Ignacio J. Ortega wrote:
Please give me some info
Shouldn't 461 be re-classified as a 4.0 issue?
ServletRequest.setCharacterEncoding is a new feature of 2.3.
- Original Message -
From: Larry Isaacs [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, September 12, 2001 8:31 AM
Subject: Remaining Tomcat 3.3 Issues
Hi All,
I have
On Wed, 12 Sep 2001, Bill Barker wrote:
Date: Wed, 12 Sep 2001 17:04:42 -0700
From: Bill Barker [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED],
Bill Barker [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: Remaining Tomcat 3.3 Issues
Shouldn't 461 be re-classified as a 4.0 issue
36 matches
Mail list logo
