Thank you for the lead, but I think this is actually the source of my issue
even in later versions of the beautifully lightweight webdav release...

This is from the <tomcat-5.5.15 installdir>webapps/webdav/WEB-INF/web.xml
file:

<!-- Using /* as the mapping ensures that jasper, welcome files etc are
       over-ridden and all requests are processed by the webdav servlet.
       This also overcomes a number of issues with some webdav clients
       (including MS Webfolders) that do not respond correctly to the
       redirects (302) that result from using a mapping of / -->
<servlet-mapping>
    <servlet-name>webdav</servlet-name>
    <url-pattern>/*</url-pattern>
</servlet-mapping>

But if I use "/*" as the servlet mapping, and if all requests are processed
by the webdav servlet, the directory is not accessible from a web browser
since the "/" request to my web application returns a directory listing
instead of returning the welcome file!

What this suggest to me is that the default webdav client does not work for
the biggest potential market for web hosting customers, i.e., windows users.
Since Microsoft's market dominance is reality (so reality bites), the webdav
servlet is not feasible as it stands...

...unless...

There is a workaround for this.  I would prefer not to give my hosting
clients the following answer:

"Get another WebDAV client..."

This means that I (and anyone else using Tomcat for hosting) lose
marketshare to Microsoft-compatible solutions since users tend to gravitate
to what is quickest and easiest.

To thwart the buffer overflow thread, I want to run pure Java web hosting.
Tomcat, IMO, is my best alternative save this one issue, and (duh) any help
would be much appreciated.

JCD

-----Original Message-----
From: Mark Thomas [mailto:[EMAIL PROTECTED] 
Sent: Monday, February 27, 2006 2:44 PM
To: Tomcat Users List
Subject: Re: WEBDAV for Tomcat 5.0.28


John C. Dale wrote:
> What is the recommended deployment of the static site and webdav 
> servlet such that direct access to the files does not go through the 
> servlet, and webdav requests do?

You'll need the webdav servlet from 5.5.x You can get this here:
http://www.apache.org/dist/java-repository/tomcat/jars/servlets-webdav-5.5.1
5.jar

The following is from:
http://svn.apache.org/repos/asf/tomcat/container/tc5.5.x/webapps/webdav/inde
x.html

To add remote authoring to your web application, you need to make the
following changes:

    * Add the webDAV servlet to your web application. See the web
application deployment descriptor for an example. Don't forget to make it
read/write.
    * Add a servlet mapping for the webDAV servlet with a url pattern of
"/webdav/*" to your web.xml.
    * Add an appropriate security constraint to prevent unauthorised changes
to your web application.
    * You can then edit your web application using a webDAV client using a
url like http://host:port/webapp/webdav


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to