Hello, me again
This should have been so easy (famous last words)
I am upgrading from tomcat jakarta-tomcat-4.0.4 to jakarta-tomcat-4.1.17
4.0.4 was working fine.
For some reason I can not find my servlets ARG!
In my web.xml I have a load-on-startup/ and in the log file , the
servlet
[mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 19, 2002 10:51 AM
To: 'Tomcat Users List'
Subject: Should not be this hard
Hello, me again
This should have been so easy (famous last words)
I am upgrading from tomcat jakarta-tomcat-4.0.4 to
jakarta-tomcat-4.1.17
4.0.4 was working fine
--- Randy Paries [EMAIL PROTECTED] wrote:
Hello, me again
This should have been so easy (famous last words)
I am upgrading from tomcat jakarta-tomcat-4.0.4 to
jakarta-tomcat-4.1.17
4.0.4 was working fine.
For some reason I can not find my servlets ARG!
I believe that the
Hello Randy,
Uncomment the invoker servlet in Tomcat's conf/web.xml
You should not be depending on the invoker servlet on production
servers. It is a security risk.
jake
Thursday, December 19, 2002, 9:50:34 AM, you wrote:
RP Hello, me again
RP This should have been so easy (famous last
not be this hard
Hello, me again
This should have been so easy (famous last words)
I am upgrading from tomcat jakarta-tomcat-4.0.4 to jakarta-tomcat-4.1.17
4.0.4 was working fine.
For some reason I can not find my servlets ARG!
In my web.xml I have a load-on-startup/ and in the log file , the
servlet
List'
Subject: RE: Should not be this hard
From the release notes
Enabling invoker servlet:
Starting with Tomcat 4.1.12, the invoker servlet is no longer available
by
default in all webapp. Enabling it for all webapps is possible by
editing
ext. 258 / Fax 202-463-4863
-Original Message-
From: Randy Paries [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 19, 2002 11:20 AM
To: 'Tomcat Users List'
Subject: RE: Should not be this hard(why is this a security risk)
That is what I needed ...
Thanks all
To follow
These messages indicate that a fix is in the works: A new Tomcat 4.1.x
release incorporating the fix to the invoker servlet will be made
available shortly.
Am I reading this correctly as saying the quick fix is to disable the
invoker, but the long term fix is to change the invoker to make the
-Original Message-
From: Larry Meadors [mailto:[EMAIL PROTECTED]]
Sent: Thursday, December 19, 2002 12:09 PM
To: [EMAIL PROTECTED]
Subject: RE: Should not be this hard(why is this a security risk)
These messages indicate that a fix is in the works: A new
Tomcat 4.1.x release
On Thu, 19 Dec 2002, Tim Moore wrote:
Date: Thu, 19 Dec 2002 12:48:37 -0500
From: Tim Moore [EMAIL PROTECTED]
Reply-To: Tomcat Users List [EMAIL PROTECTED]
To: Tomcat Users List [EMAIL PROTECTED]
Subject: RE: Should not be this hard(why is this a security risk)
-Original Message
, December 19, 2002 10:19 AM
Subject: RE: Should not be this hard(why is this a security risk)
That is what I needed ...
Thanks all
To follow this up, why is this a security risk?
Do they want specific mapping for each servlet?
Thanks
-Original Message-
From: PELOQUIN,JEFFREY
11 matches
Mail list logo