Diskussion:Plone 3.1 installieren: Unterschied zwischen den Versionen
K (hat „Diskussion:Installationsanleitungen:Plone 3.1“ nach „Diskussion:Plone 3.1 installieren“ verschoben: Wenn die Installationsanleitungen mit dem Namen der Software beginnen, werden sie in der Kategorie:Installationsanleitungen nicht alle) |
Dgy00 (Diskussion | Beiträge) Keine Bearbeitungszusammenfassung |
||
| Zeile 1: | Zeile 1: | ||
Enabling WebDAV in Zope | |||
You must enable the WebDAV port in your Zope config to use it. Add the following to zope.conf: | |||
<webdav-source-server> | |||
# valid keys are "address" and "force-connection-close" | |||
address www.mydomain.com:1980 | |||
force-connection-close off | |||
</webdav-source-server> | |||
This will enable the WebDAV server on http://www.mydomain.com:1980/. Note that you cannot use this URL in your web browser, just in WebDAV clients. Using the web browser will give you an error message AttributeError: manage_FTPget. You could also just run the WebDAV server on localhost with address 1980, forcing you to either use a WebDAV client locally or proxy WebDAV through Apache. | |||
A way to cope with the port problems with Zope is to use Apache's Rewrite rules to ProxyPass the URL /dav or a seperate vhost dav.site.com to the seperate WebDAV port, usually 1980. This way, clients can use just http://www.site.com/dav/ or http://dav.site.com/. This makes it possible to access WebDAV even from behind a strict firewall. | |||
You will have to find out what the URL to your WebDAV service will be. In this document, the URL http://plone.s11.no/dav/felles/s11 will be used as an example. This is a rewrite /dav on the vhost plone.s11.no, and felles/s11 is the path to the Plone instance inside Zope, as shown in the Zope management interface /manage. By using the full path to the Plone instance WebDAV clients can log in using the normal Plone user instead of the global zope user. | |||
Version vom 21. Februar 2009, 22:03 Uhr
Enabling WebDAV in Zope
You must enable the WebDAV port in your Zope config to use it. Add the following to zope.conf:
<webdav-source-server> # valid keys are "address" and "force-connection-close" address www.mydomain.com:1980 force-connection-close off </webdav-source-server>
This will enable the WebDAV server on http://www.mydomain.com:1980/. Note that you cannot use this URL in your web browser, just in WebDAV clients. Using the web browser will give you an error message AttributeError: manage_FTPget. You could also just run the WebDAV server on localhost with address 1980, forcing you to either use a WebDAV client locally or proxy WebDAV through Apache.
A way to cope with the port problems with Zope is to use Apache's Rewrite rules to ProxyPass the URL /dav or a seperate vhost dav.site.com to the seperate WebDAV port, usually 1980. This way, clients can use just http://www.site.com/dav/ or http://dav.site.com/. This makes it possible to access WebDAV even from behind a strict firewall.
You will have to find out what the URL to your WebDAV service will be. In this document, the URL http://plone.s11.no/dav/felles/s11 will be used as an example. This is a rewrite /dav on the vhost plone.s11.no, and felles/s11 is the path to the Plone instance inside Zope, as shown in the Zope management interface /manage. By using the full path to the Plone instance WebDAV clients can log in using the normal Plone user instead of the global zope user.