> How do I implement security using the WebdavServlet? mod_dav uses a > standard .htpasswd file to track the various developers' logins, is > this similar?
It uses the standard security provided by the container. > Can I limit the types of DAV actions that can be performed? It's either read or read/write. > Where is the DAV lock information stored? In memory. > Does anyone know the possible init-params for the WebdavServlet? I got > these from the web.xml in the example, but are there other params?: > > <servlet> > <servlet-name>webdav</servlet-name> > > <servlet-class>org.apache.catalina.servlets.WebdavServlet</servlet-class> > <init-param> > <param-name>debug</param-name> > <param-value>0</param-value> > </init-param> > <init-param> > <param-name>listings</param-name> > <param-value>true</param-value> > </init-param> > <!-- Uncomment this to enable read and write access --> > <init-param> > <param-name>readonly</param-name> > <param-value>false</param-value> > </init-param> > <load-on-startup>1</load-on-startup> > </servlet> No. It's quite rudimentary overall (just allows uploading and resource manipulation). Remy -- To unsubscribe: <mailto:[EMAIL PROTECTED]> For additional commands: <mailto:[EMAIL PROTECTED]> Troubles with the list: <mailto:[EMAIL PROTECTED]>
