Open source, commercial support.
- Integrate with FCKEditor
- Using the displayname field
- Character encoding
- Client compatibility
- Efficient deleting
- Connecting to webdav
- Caching and Modified Dates
- Configuration
- Open folder from web page
- Using Caldav
- Create your own dav servlet
- Custom Webdav Properties with Annotation
- Http logging and DebugFilter
- How to support PROPPATCH
- Users Guide
- Modules
- Integrating with non servlet applications
- Permission Dependent Resources
- Running on the root context
- Security in webdav: Authenticate and Authorise
- Test scripts
- Using milton with jquery datatable
- ZSync
When debugging a webdav application its very often helpful to see the exact request and responses.
The best way to do this is to use a network sniffing tool like wireshark, but that doesnt work in some important circumstances:
- when running on localhost (because request dont go to an actual network adapter)
- when using SSL
The solution is to use Milton's DebugFilter. This is a Milton filter (NOT a javax.servlet filter!) which writes text files containing each request and response to some directory.
Caution: Using DebugFilter can create ten's of thousands of files in your home directory. This can bring your PC to its knees! Turn it on when you need it then turn it off
How to use it
Using servlet configuration:
<init-param>
<param-name>filter_0</param-name>
<param-value>com.bradmcevoy.http.DebugFilter</param-value>
</init-param>
Using Spring configuration:
<bean id="milton.debug.filter" class="com.bradmcevoy.http.DebugFilter" >
<constructor-arg value="/somedir"/>
</bean>
<bean id="milton.http.manager" class="com.bradmcevoy.http.HttpManager">
<constructor-arg ref="milton.resource.factory" />
<property name="filters">
<list>
<ref bean="milton.debug.filter" />
</list>
</property>
</bean>