On Wed, 2004-10-27 at 15:31, John Poltorak wrote:
On Tue, Oct 26, 2004 at 09:22:42PM +0200, Tino Wildenhain wrote:
Hi,
Am Di, den 26.10.2004 schrieb John Poltorak um 21:09:
Is Zope enabled for Webdav by default or does something specific need to be set?
As far as a Webdav enabled client, will recent versions of Mozilla (1.73) be OK for using Webdav and how would I get them into Webdav mode?
Zope enables webdav by default. There is a second server which is referred to as "webdav source server" which just means "GET" will return document_src instead of rendered content. The web port will behave same for all dedicated webdav clients it knows.
What port does it use? I guess I can tell whether it is available by running 'netstat -l'...
This Port: <http-server> # valid keys are "address" and "force-connection-close" address 8080 # force-connection-close on webdav-source-clients Konqueror </http-server> (zope.conf) Here you see the example to force a client based on its user-agent string to receive source nistead of rendered output. (The webdav-source-clients Konqueror line) This is the usual web port in case you wonder. For most clients this is not necessary because their signature is known by Zope.
I'm not aware where Mozilla is a webdav client. Do you mean the HTML author module?
Mozilla's Calendar app can use WebDAV for maintaing a remote calendar.
Hm. try your luck. Sometimes it helps if you save the file locally, load it up once via ZMI and then open it from there in your client app. Regards Tino