the MS Windows/Office webdav client code (distinct from the webdav client code
you have if you don't have Office -- doncha just LOVE Windows?) makes frequent
HTTP 1.1 OPTIONS calls and needs to see an 'MS-Author-Via: DAV' header to be happy.
Also, if you're running Plone it makes GET calls that trigger some versions of
manage_FTPget that are mapped to index_html calls that need parameters.
Thus the attached patch; It's only tested a very little so far, but Explorer
is suddenly actually showing folders on our site with apache proxying via SSL...
Uploaded: Resource_py_diff
According to:
http:// www.zorched. net/2006/ 03/01/more- webdav- tips-tricks- and-bugs/
the MS Windows/Office webdav client code (distinct from the webdav client code
you have if you don't have Office -- doncha just LOVE Windows?) makes frequent
HTTP 1.1 OPTIONS calls and needs to see an 'MS-Author-Via: DAV' header to be happy.
Also, if you're running Plone it makes GET calls that trigger some versions of
manage_FTPget that are mapped to index_html calls that need parameters.
Thus the attached patch; It's only tested a very little so far, but Explorer
is suddenly actually showing folders on our site with apache proxying via SSL...