Amy Roh wrote:
K. I can reproduce the problem with 4.1.30 build but not in the workspace.
Looks like the latest org.apache.coyote.tomcat4.CoyoteConnector with
allowTrace didn't get tagged for 4.1.30. 4.1.30 tag has outdated
o.a.c.tomcat4.CoyoteConnector
4.1.30 was tagged about one month befor
Yeah, that's what it looked like. Larry's backport of the "allowTrace"
stuff in the connector code came after the TOMCAT_4_1_30 tag, whereas in
the admin application, the file that wanted to look for the allowTrace,
in EditConnectorAction.java WAS tagged with 4.1.30
>>> [EMAIL PROTECTED] 2/27/04
K. I can reproduce the problem with 4.1.30 build but not in the workspace.
Looks like the latest org.apache.coyote.tomcat4.CoyoteConnector with
allowTrace didn't get tagged for 4.1.30. 4.1.30 tag has outdated
o.a.c.tomcat4.CoyoteConnector
Amy
---
I just did the following steps:
1) downloaded jakarta-tomcat-4.1.30.zip from jakarta.apache.org
2) unzipped the zip file
3) edited conf\tomcat-users.xml, adding the "admin" and "manager" roles
to the "tomcat" user
4) Start up Tomcat (catalina start)
5) hit http://localhost:8080
6) Navigate to the "
I can't reproduce this one either. Clean install might be the answer...
> Yeah, I saw this on a newly-downloaded Tomcat 4.1.30 on SUSE linux 8.2,
> java 1.3.1 (Sun?) I first saw it on NetWare, JVM 1.4.2. I thought it
> was something I had done wrong on NetWare, so I quickly tried it on
> Linux
your 4.1.30 consistently show this problem without your patch?
Cheers,
Larry
> -Original Message-
> From: Jeff Tulley [mailto:[EMAIL PROTECTED]
> Sent: Friday, February 27, 2004 3:48 PM
> To: [EMAIL PROTECTED]
> Subject: Re: allowTrace attribute causing problems in the
>
,
Larry
> -Original Message-
> From: Jeff Tulley [mailto:[EMAIL PROTECTED]
> Sent: Friday, February 27, 2004 3:48 PM
> To: [EMAIL PROTECTED]
> Subject: Re: allowTrace attribute causing problems in the
> adminapplication
>
>
> Actually, if I am not mistake
