I figured out the problem and it is a bug in Tomcat-4.1.19. Actually, it
is more of an oversight. The servlet-mapping /deploy wasn't specified in
the manager's web.xml. See details about it here.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16243
Hopefully, this can be fixed by the
I have always used the install task, so I haven't run into this issue
until now. I have a .war file which I want to deploy to Tomcat. The path
is correct because I've tried the same file:/// URL to do an install from
the manager web GUI and that was successful. I also use the same path,
