Nigel, there are two related problems: - Zope makes some checks against HTTP_USER_AGENT inside the WebDav staff. However Dreamweaver does not send a user-agent string for WebDAV request. This caused some problems. A fix will be in the next release or in the CVS - When DW tries to lock a file it sends a lock request without authorization headers. Zope answers with a 401 response (unauthorized) and DW propagates this error to the user instead of re-trying with the corresponding username/password credentials. So this is really a DW related problem, not a Zope problem. Andreas Zope Corporation ----- Original Message ----- From: "Nigel Head" <nhead@houbits.com> To: <zope@zope.org> Sent: Montag, 6. August 2001 00:11 Subject: [Zope] Dreamweaver WebDAV & locking ??

I'm sure someone cleverer than I knows how this should work.

Zope 2.4.0, Python 2.1.1, Dreamweaver 4.01

When creating a file for the first time with webdav DW attempts to lock the resource, Zope creates Nullresource-Lock item as a placeholder (all well and good, I thought) but then DW fails to upload the real contents claiming either 'Resource locked' or 'Resource not found'. I haven't been able to figure the system which selects one or other of these two replies.

This smells of pilot error to me so please, anyone who sucessfully uses DW webdav, do you have a takeoff checklist ??

Thanks,

Nigel.

_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )