[Zope] dreamweaver WebDAV confusion

[Milos Prudek]

I run Zope with WebDAV source port. Dreamweaver MX 2004 authenticates 
successfully and I can browse directories.

To avoid problems, I use extensions. I created an "a.zpt" Page Template 
in the ZMI.

When I double-click it in Dreamweaver, dw checks it out (green check 
mark displayed next to the a.zpt file) but dw will display nothing. dw 
behaves as if no file was opened. No error message.

Below is the contents of TCP communication on the webdav port when I 
double-click "a.zpt". As you can see, the a.zpt file contents is not 
downloaded.

What gives?

PROPFIND /www.ibc.cz/test/ HTTP/1.1.
Host: 172.16.38.1:3980.
User-Agent: Dreamweaver-WebDAV-SCM1.02.
Authorization: Basic bWlsOnplbk1hbmFnZXI=.
Translate: f.
Depth: 1.
Connection: Close.
Content-Type: text/xml; charset="utf-8".
Content-Length: 130.
.
<?xml version="1.0" encoding="utf-8" ?>.
<D:propfind xmlns:D="DAV:">.
.<D:prop>.
..<D:resourcetype/>.
</D:prop>.
</D:propfind>.
.
HTTP/1.1 207 Multi-Status.
Server: Zope/(unreleased version, python 2.3.3, linux2) ZServer/1.1.
Date: Thu, 01 Apr 2004 17:51:10 GMT.
Content-Length: 1753.
Connection: close.
Ms-Author-Via: DAV.
Connection: close.
Etag: .
Date: Thu, 01 Apr 2004 17:51:10 GMT.
Content-Type: text/xml; charset="utf-8".
.
<?xml version="1.0" encoding="utf-8"?>
<d:multistatus xmlns:d="DAV:">
<d:response>
<d:href>/www.ibc.cz/test/</d:href>
<d:propstat>
   <d:prop>
<n:resourcetype xmlns:n="DAV:"><n:collection/></n:resourcetype>
   </d:prop>
   <d:status>HTTP/1.1 200 OK</d:status>
</d:propstat>
</d:response>
<d:response>
<d:href>/www.ibc.cz/test/a</d:href>
<d:propstat>
   <d:prop>
<n:resourcetype xmlns:n="DAV:"></n:resourcetype>
   </d:prop>
   <d:status>HTTP/1.1 200 OK</d:status>
</d:propstat>
</d:response>
<d:response>
<d:href>/www.ibc.cz/test/insert</d:href>
<d:propstat>
   <d:prop>
<n:resourcetype xmlns:n="DAV:"></n:resourcetype>
   </d:prop>
   <d:status>HTTP/1.1 200 OK</d:status>
</d:propstat>
</d:response>
<d:response>
<d:href>/www.ibc.cz/test/insert_cz</d:href>
<d:propstat>
   <d:prop>
<n:resourcetype xmlns:n="DAV:"></n:resourcetype>
   </d:prop>
   <d:status>HTTP/1.1 200 OK</d:status>
</d:propstat>
</d:response>
<d:response>
<d:href>/www.ibc.cz/test/insert_sample</d:href>
<d:propstat>
   <d:prop>
<n:resourcetype xmlns:n="DAV:"></n:resourcetype>
   </d:prop>
   <d:status>HTTP/1.1 200 OK</d:status>
</d:propstat>
</d:response>
<d:response>
<d:href>/www.ibc.cz/test/select</d:href>
<d:propstat>
   <d:prop>
<n:resourcetype xmlns:n="DAV:"></n:resourcetype>
   </d:prop>
   <d:status>HTTP/1.1 200 OK</d:status>
</d:propstat>
</d:response>
<d:response>
<d:href>/www.ibc.cz/test/untitled.htm</d:href>
<d:propstat>
   <d:prop>
<n:resourcetype xmlns:n="DAV:"></n:resourcetype>
   </d:prop>
   <d:status>HTTP/1.1 200 OK</d:status>
</d:propstat>
</d:response>
<d:response>
<d:href>/www.ibc.cz/test/a.zpt</d:href>
<d:propstat>
   <d:prop>
<n:resourcetype xmlns:n="DAV:"></n:resourcetype>
   </d:prop>
   <d:status>HTTP/1.1 200 OK</d:status>
</d:propstat>
</d:response>
</d:multistatus>

-- 
Milos Prudek
_________________
Most websites are
confused chintzy gaudy conflicting tacky unpleasant... unusable.
Learn how usable YOUR website is! http://www.spoxdesign.com