-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Michael Dexter wrote:

It appears that Apache and IIS put both HTTP and WebDAV/HTTP traffic over the same port. Can Zope do the same? Why? Why not?

You *can* do WebDAV over the normal HTTP port -- it works a treat for non-code-like objects (images, files, etc.) but is problematic for objects whose rendering is more than just the bits stored on the object, e.g. scripts, templates. DAV isn't terribly useful for the rendered output of those objects; the "WebDAV source port" allows you to perform DAV operations against the *unrendered* source of the script / template. Tres. - -- =================================================================== Tres Seaver +1 202-558-7113 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDl1Sj+gerLs4ltQ4RAtVWAKCcWG1v/UOERC3yBg6EwWK8wFKAowCfav1a rRuYU92SvgQ34NS5NpKVFcA= =rAfA -----END PGP SIGNATURE-----

Michael Dexter wrote:

Hello,

It appears that Apache and IIS put both HTTP and WebDAV/HTTP traffic over the same port. Can Zope do the same? Why? Why not?

What I usually do is to create a RewriteRule in apache, that rewrites to the dav port. RewriteRule ^/webdav(.*) http://localhost:1981/VirtualHostBase/http/www.example.com:80/plone_instance... [P,L] So that the webdav port can be gotten to at: http://www.example.com:80/webdav -- hilsen/regards Max M, Denmark http://www.mxm.dk/ IT's Mad Science