1,870
edits
Changes
Jump to navigation
Jump to search
Line 17:
Line 17: − + + + +
How to set up a secure webdav area on an Apache 2.0 server that is mountable from windows (view source)
Revision as of 02:54, 29 August 2007
, 02:54, 29 August 2007→Authentication with a Client Certificate
This seemed to work at first, in that I was able to access files using the normal Windows explorer interface. This seems to be because explorer had cached the directory contents from a former session, because a bit later I tried to refresh the window and it failed with the following complaint
This seemed to work at first, in that I was able to access files using the normal Windows explorer interface. This seems to be because explorer had cached the directory contents from a former session, because a bit later I tried to refresh the window and it failed with the following complaint
<pre>
<pre>
Documents in this folder are not available. The folder may have been moved or deleted, or network problems may be preventing a connection to the server.
Documents in this folder are not available.
The folder may have been moved or deleted,
or network problems may be preventing a connection
to the server.
</pre>
</pre>
The Apache server ssl error logs showed SSL library error reason code 199, which means that the client did not provide a client certificate. It seems that the Windows XP webdav client is not smart enough to supply a client certificate, even though the interface that explorer uses to fetch a file from the same directory (probably a ie component) does. Bummer.
The Apache server ssl error logs showed SSL library error reason code 199, which means that the client did not provide a client certificate. It seems that the Windows XP webdav client is not smart enough to supply a client certificate, even though the interface that explorer uses to fetch a file from the same directory (probably a ie component) does. Bummer.