Am Samstag, 24. September 2005 01:08 schrieb David Bear:
I run zope in back of apache, and let apache handle tls/ssl.
In all the searching on zope.org http://zope.org though I haven't found
any documents on how to let apache handle securing webdav for zope as well.
Anyone see/written such?
Hi Sascha. I realize that you can forward a port this way but this
requires providing server accounts to users in addition to zope
accounts. scponly is a product to remove other shell functionality -
so you can hand out accounts in a more untrusted situation. Either
way, handing out server
Am Samstag, den 24.09.2005, 00:29 -0300 schrieb David Pratt:
Hi Tino. Over HTTP is not the problem. It is more on normally https you
are rewriting your requests to port 443 with apache proxy and your
usual webdav server is port 1980 that is not secure.
Ah so. I use webdav over the standard
Am Samstag, den 24.09.2005, 13:39 +0200 schrieb Sascha Ottolski:
Am Samstag, 24. September 2005 01:08 schrieb David Bear:
I run zope in back of apache, and let apache handle tls/ssl.
In all the searching on zope.org http://zope.org though I haven't found
any documents on how to let apache
Am Samstag, 24. September 2005 01:08 schrieb David Bear:
I run zope in back of apache, and let apache handle tls/ssl.
In all the searching on zope.org http://zope.org though I haven't found
any documents on how to let apache handle securing webdav for zope as well.
Anyone see/written such?
I run zope in back of apache, and let apache handle tls/ssl.
In all the searching on zope.org though I haven't found any documents
on how to let apache handle securing webdav for zope as well.
Anyone see/written such?-- David BearWhat's the difference between private knowledge and public
Am Freitag, den 23.09.2005, 16:08 -0700 schrieb David Bear:
I run zope in back of apache, and let apache handle tls/ssl.
In all the searching on zope.org though I haven't found any documents
on how to let apache handle securing webdav for zope as well.
Anyone see/written such?
webdav
Hi Tino. Over HTTP is not the problem. It is more on normally https you
are rewriting your requests to port 443 with apache proxy and your
usual webdav server is port 1980 that is not secure.
I am in the same boat as David. I haven't got my webdav running
securely at this point either. The