Hi,
http://greenbytes.de/tech/webdav/webdav-redirector-list.html http://greenbytes.de/tech/webdav/webfolder-client-list.html
Seen in the light of this, what would you recommend as a robust setup? Does Slide put in any extra effort to work around MS client deficiencies?
My list of considerations for a robust setup so far:
1. Apache running HTTPS in front of Slide (ProxyPass via HTTP) 2. Apache proxies so a fixed port is not needed in the URL 3. Apache uses mod_auth_msfix for BasicAuth fixes 4. Apache rewrites URLs so DAV repositories are root folders, eg. http://dav.foo.myhost.com/ proxies to http://myhost.com:8080/dav/foo/
I'm curious: how is URL rewriting supposed to work with WebDAV? For instance, PROPFIND response bodies contain URLs that will not get rewritten on their way back to the client, right?
Julian
-- <green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
