I have a zope instance listening on localhost. I use apache and fastcgi to reach zope. Now I would like to provide webdav. Since my apache is already doing ssl, I wanted webdav connections to also go through apache. when I use cadaver and connect to my zope zope through apache, all works well even though I have specified in my zope.conf file that webdav listen on localhost:8088 (it seems that cadaver is smart enough working through the fastcgi interface to just work). When attempting to using dreamweaver mx or windows webfolders to connect to zope I get an error. So I attempted to use an apache proxy pass directive to campture all urls at myzopeserver.edu:8088/webdav back to localhost:8088. This had no effect. cadaver was still able to work. Dreamweaver (using webdav site setup) and windows webfolders still failed. What deep magic do I need to make dav work through apache? ( would prefer to have all things go through fastcgi but I understand the trend is to use proxy-pass ) -- David Bear What's the difference between private knowledge and public knowledge?
On 06/12/05, David Bear <dwbear75@gmail.com> wrote:
I have a zope instance listening on localhost. I use apache and fastcgi to reach zope. Now I would like to provide webdav. Since my apache is already doing ssl, I wanted webdav connections to also go through apache.
when I use cadaver and connect to my zope zope through apache, all works well even though I have specified in my zope.conf file that webdav listen on localhost:8088 (it seems that cadaver is smart enough working through the fastcgi interface to just work).
When attempting to using dreamweaver mx or windows webfolders to connect to zope I get an error.
So I attempted to use an apache proxy pass directive to campture all urls at myzopeserver.edu:8088/webdav back to localhost:8088. This had no effect. cadaver was still able to work. Dreamweaver (using webdav site setup) and windows webfolders still failed.
What deep magic do I need to make dav work through apache? ( would prefer to have all things go through fastcgi but I understand the trend is to use proxy-pass )
I just got this working myself, although I am using apache as a proxy, not fastcgi. If you already have ssl working with apache and can access zope through apache without ssl, it shouldn't be difficult. The main thing is to add a virtual host in your apache config for SSL and modify the rewrite line to use https:. I found the following document helpful: http://www.zope.org/Members/tmckibben/HowTo.2004-04-13.0659 It uses FastCGI, so it should more closely match your setup than mine -- Take care, eh. Chris
On Mon, 05 Dec 2005 18:17:38 -0700, David Bear wrote:
I have a zope instance listening on localhost. I use apache and fastcgi to reach zope. Now I would like to provide webdav. Since my apache is already doing ssl, I wanted webdav connections to also go through apache.
when I use cadaver and connect to my zope zope through apache, all works well even though I have specified in my zope.conf file that webdav listen on localhost:8088 (it seems that cadaver is smart enough working through the fastcgi interface to just work).
When attempting to using dreamweaver mx or windows webfolders to connect to zope I get an error.
So I attempted to use an apache proxy pass directive to campture all urls at myzopeserver.edu:8088/webdav back to localhost:8088. This had no effect. cadaver was still able to work. Dreamweaver (using webdav site setup) and windows webfolders still failed.
What deep magic do I need to make dav work through apache? ( would prefer to have all things go through fastcgi but I understand the trend is to use proxy-pass )
I believe this patch is required if using recent WinXP, due to Microsoft webdav breakages: http://teyc.editthispage.com/2005/06/02 It fixed webdav for web folder for me. Add the extra line into the OPTIONS method of the file mentioned, where other headers are being set. -- Sam.
David Bear wrote:
I have a zope instance listening on localhost. I use apache and fastcgi to reach zope.
you may wish to rethink that when you get a chance...
Now I would like to provide webdav.
What do you want to use WebDAV for?
when I use cadaver and connect to my zope zope through apache, all works well even though I have specified in my zope.conf file that webdav listen on localhost:8088 (it seems that cadaver is smart enough working through the fastcgi interface to just work).
I know nothing abotu fastcgi, but I doubt you're reachign the source port, so if you open a ZPT, for example, you will get the rendered version, and if you edit and save it, you will loose all your tal markup.
When attempting to using dreamweaver mx or windows webfolders to connect to zope I get an error.
Chocolate teapot? ;-) What error, exactly and verbosely, did you get?
So I attempted to use an apache proxy pass directive to campture all urls at myzopeserver.edu:8088/webdav back to localhost:8088. This had no effect.
I doubt it had no effect, look in your apache access and error logs...
cadaver was still able to work. Dreamweaver (using webdav site setup) and windows webfolders still failed.
More information please... you may need to get a packet sniffer such as etheral up and running to get further... cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
Hi Folks. I have an existing (and working) Zope install, but I'm trying to get modern here... I'm having trouble getting Zope 2.8.4 to make properly - keeps complaining "operation not permitted" when copying a file from the zope directory to the build directory. Like so: "/usr/local/bin/python" "<myhomedirectory>/Zope-2.8.4-final/setup.py" \ build --build-base="<myhomedirectory>/Zope-2.8.4-final/ build-base/python-2.4" --build-lib="<myhomedirectory>/Zope-2.8.4- final/build-base/python-2.4/build-lib" --build- scripts="<myhomedirectory>/Zope-2.8.4-final/build-base/python-2.4/ build-scripts" --build-temp="<myhomedirectory>/Zope-2.8.4-final/build- base/python-2.4/build-temp" running build running build_py copying zope/component/tests/__init__.py -> <myhomedirectory>/ Zope-2.8.4-final/build-base/python-2.4/build-lib/zope/component/tests error:<myhomedirectory>/Zope-2.8.4-final/build-base/python-2.4/build- lib/zope/component/tests/__init__.py: Operation not permitted make: *** [build] Error 1 Obviously I've substituted <myhomedirectory> for the actual path. This error is what I get if I run make as root - if I run as a user, I get "Permission denied". Any idea what's hanging this up? TIA...
Sam Moore wrote at 2005-12-6 10:41 -0500:
... copying zope/component/tests/__init__.py -> <myhomedirectory>/ Zope-2.8.4-final/build-base/python-2.4/build-lib/zope/component/tests error:<myhomedirectory>/Zope-2.8.4-final/build-base/python-2.4/build- lib/zope/component/tests/__init__.py: Operation not permitted
Apparently, copying "zope/component/tests/__init__.py" to "<myhomedirectory>/>Zope-2.8.4-final/build-base/python-2.4/build-lib/zope/component/tests/__init__.py" fails.
Obviously I've substituted <myhomedirectory> for the actual path. This error is what I get if I run make as root - if I run as a user, I get "Permission denied".
Is "<myhomedirectory>" an NFS mount? Then, there are probably special restrictions for "root" use. Does the (non root) user have write permissions on "<myhomedirectory>"? -- Dieter
On Dec 6, 2005, at 3:02 PM, Dieter Maurer wrote:
Sam Moore wrote at 2005-12-6 10:41 -0500:
... copying zope/component/tests/__init__.py -> <myhomedirectory>/ Zope-2.8.4-final/build-base/python-2.4/build-lib/zope/component/tests error:<myhomedirectory>/Zope-2.8.4-final/build-base/python-2.4/build- lib/zope/component/tests/__init__.py: Operation not permitted
Apparently, copying "zope/component/tests/__init__.py" to "<myhomedirectory>/>Zope-2.8.4-final/build-base/python-2.4/build- lib/zope/component/tests/__init__.py" fails.
Well no, actually - the file gets copied! i checked. But make stops at that point.
Obviously I've substituted <myhomedirectory> for the actual path. This error is what I get if I run make as root - if I run as a user, I get "Permission denied".
Is "<myhomedirectory>" an NFS mount? Then, there are probably special restrictions for "root" use.
No, it's local.
Does the (non root) user have write permissions on "<myhomedirectory>"?
yes, it's that user's own directory. I chown'ed everything in it to make sure the user was the owner, and got similar results (on a different file name, but same scenario).
-- Dieter
Sam Moore wrote at 2005-12-6 16:59 -0500:
...
copying zope/component/tests/__init__.py -> <myhomedirectory>/ Zope-2.8.4-final/build-base/python-2.4/build-lib/zope/component/tests error:<myhomedirectory>/Zope-2.8.4-final/build-base/python-2.4/build- lib/zope/component/tests/__init__.py: Operation not permitted
Apparently, copying "zope/component/tests/__init__.py" to "<myhomedirectory>/>Zope-2.8.4-final/build-base/python-2.4/build- lib/zope/component/tests/__init__.py" fails.
Well no, actually - the file gets copied! i checked. But make stops at that point.
It is likely that the copying process wants to modify permissions and/or access times and that this raises the "Operation not permitted" error. -- Dieter
On Dec 7, 2005, at 3:10 PM, Dieter Maurer wrote:
Sam Moore wrote at 2005-12-6 16:59 -0500:
...
copying zope/component/tests/__init__.py -> <myhomedirectory>/ Zope-2.8.4-final/build-base/python-2.4/build-lib/zope/component/ tests error:<myhomedirectory>/Zope-2.8.4-final/build-base/python-2.4/ build- lib/zope/component/tests/__init__.py: Operation not permitted
Apparently, copying "zope/component/tests/__init__.py" to "<myhomedirectory>/>Zope-2.8.4-final/build-base/python-2.4/build- lib/zope/component/tests/__init__.py" fails.
Well no, actually - the file gets copied! i checked. But make stops at that point.
It is likely that the copying process wants to modify permissions and/or access times and that this raises the "Operation not permitted" error.
That sounds reasonable, but if I'm root (or the owner of the directory, for that matter) at the time I run make, what else can I do to get out of it? Does the whole directory need to be world-writable?
-- Dieter
On Dec 8, 2005, at 9:51 AM, Sam Moore wrote:
On Dec 7, 2005, at 3:10 PM, Dieter Maurer wrote:
Sam Moore wrote at 2005-12-6 16:59 -0500:
...
copying zope/component/tests/__init__.py -> <myhomedirectory>/ Zope-2.8.4-final/build-base/python-2.4/build-lib/zope/component/ tests error:<myhomedirectory>/Zope-2.8.4-final/build-base/python-2.4/ build- lib/zope/component/tests/__init__.py: Operation not permitted
Apparently, copying "zope/component/tests/__init__.py" to "<myhomedirectory>/>Zope-2.8.4-final/build-base/python-2.4/ build- lib/zope/component/tests/__init__.py" fails.
Well no, actually - the file gets copied! i checked. But make stops at that point.
It is likely that the copying process wants to modify permissions and/or access times and that this raises the "Operation not permitted" error.
That sounds reasonable, but if I'm root (or the owner of the directory, for that matter) at the time I run make, what else can I do to get out of it?
Does the whole directory need to be world-writable?
Just answered my own question - this doesn't help.
-- Dieter
_______________________________________________ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists -http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Sam Moore wrote at 2005-12-8 09:51 -0500:
...
It is likely that the copying process wants to modify permissions and/or access times and that this raises the "Operation not permitted" error.
That sounds reasonable, but if I'm root (or the owner of the directory, for that matter) at the time I run make, what else can I do to get out of it?
You must locate the precise place where the exception is raised. This should tell us what operation precisely is not permitted and we may then be able to understand why. -- Dieter
participants (6)
-
Chris Purves -
Chris Withers -
David Bear -
Dieter Maurer -
Sam Moore -
Sam Stainsby