Mona Wong-Barnum [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
Sorry, I'm a moron, I commented out the wrong section in web.xml for the
vulnerability (:
All is well, 4.0.5 is now working for me.
With 4.0.5, does it matter if the section in web.xml about
Bill Barker wrote:
Mona Wong-Barnum [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
Sorry, I'm a moron, I commented out the wrong section in web.xml for the
vulnerability (:
All is well, 4.0.5 is now working for me.
With 4.0.5, does it matter if the section
Barker [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 26, 2002 3:55 AM
To: [EMAIL PROTECTED]
Subject: Re: tomcat 4.0.5 not serving HTML pages
Mona Wong-Barnum [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
Sorry, I'm a moron, I comme
Make sure the DefaultServlet is still active, its the
InvokerServlet that gets you into trouble.
Read the text about it at:
http://jakarta.apache.org/site/news.html#0924.1
--- Mona Wong-Barnum [EMAIL PROTECTED] wrote:
Due to the recent security vulnerability, I've
upgrade to 4.0.5.
Sorry, my initial reply got filtered by some kind of
language censor.
Anyway, you need to make sure that your /conf/web.xml
has the DefaultServlet active. The DefaultServlet is
responsible for serving static content.
The most recent version of Tomcat tinkers a bit with
the InvokerServlet,
