I'd love to reply but your spam filter keeps bumping my messages back: >This Message was undeliverable due to the following reason: > >Your message is larger than the destination computer is willing to accept, >so it was returned. The error message below indicates the size of your >message and the maximum size allowed by the receiving E-mail system. You >may be able to split your message into several smaller pieces and have them >delivered separately. > >Your message was rejected by mx1.eu.apache.org for the following reason: > > spam score (5.0) exceeded threshold > >The following recipients did not receive this message: > > <[email protected]> > >Please reply to <[EMAIL PROTECTED]> if you feel this message to be >in error.
Message size is about 8k so that can't really be an issue Any suggestions -----Original Message----- From: Julian Reschke [mailto:[EMAIL PROTECTED] Sent: Tuesday, 29 January 2008 9:26 PM To: [email protected] Subject: Re: problems with lock-depth infinity Roland Porath wrote: > All the webdav clients I've looked at so far seem to default to an infinite > lock depth even if the resource is not a collection. Lock depth infinity simply is the default, and from WebDAV's point of view, for non-collection resources the semantics are exactly the same. So there's really no reason not to stick with the default. > Jackrabbit does not seem to like that and is not able to remove the lock. > > Now the question: is that a bug or a feature. It does not make a lot of > sense to have an infinite lock depth on a non collection so jackrabbit would > be justified to whinge. On the other hand the clients (and slide webdav > server) seem to have a different opinion. As Angela said: more information required. Does the LOCK request fail? If it didn't, what does PROPFIND on DAV:lockdiscovery reveal? BR, Julian !DSPAM:479eff6b86197663616762!
