Web folder mapping allows users to map web folder to the file system on local computer (WebDav). Users may see on a local computer and work with the same folders that they see in HTTP Commander interface with the same rights. In fact the work with files takes place online in a remote folder on server, so Internet access is necessary. All the changes made by a user apply to the files on server at the very same moment.
Advantages of web folder:
<configuration> ... <system.web> ... <httpModules> ... <add name="FileWebDavModule" type="HttpCommander.FileWebDAVServer.FileWebDavModule, FileWebDAVServer" /> ... </httpModules> ... </system.web> ... <system.webServer> ... <modules runAllManagedModulesForAllRequests="true"> <remove name="FileWebDavModule" /> <remove name="WebDAVModule" /> ... <add name="FileWebDavModule" type="HttpCommander.FileWebDAVServer.FileWebDavModule, FileWebDAVServer" preCondition="integratedMode" /> ... </modules> ... </system.webServer> ... </configuration>
Turning off ASP.NET URL authorization on WebDav folder.
Make sure the following section is present in application's Web.config file.
<location path="hcwebdav"> <system.web> <authorization> <allow users="*" /> </authorization> </system.web> </location>
(Path attribute must match IdentifierWebDav parameter.)
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ASP.NET\VerificationCompatibility HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\ASP.NET\VerificationCompatibilityor download and run AspNetVerificationCompatibility.reg file.
A URL of a web folders looks like "http://www.yoursite.com/HTCOMNET/hcwebdav/" or "http://www.yoursite.com/HTCOMNET/hcwebdav/0/". "www.yoursite.com/HTCOMNET" should be replaced with real path. "hcwebdav" is an artificial path component serving to identify WebDav requests. This is not a real folder in the application root folder! Don't remove this component from URL! You may change this suffix with the IdentifierWebDav HTTP Commander setting (hidden by default). If for the AnonymousEditingOffice parameter indicated value of true, is mandatory presence of a suffix "0" — "0" path component classifies this WebDav URL as normal WebDav URL requiring authentication. If you need to designate a specific folder, then append the folder path after /hcwebdav/ or /hcwebdav/0/ suffix, for example, "http://www.yoursite.com/HTCOMNET/hcwebdav/foldername" or "http://www.yoursite.com/HTCOMNET/hcwebdav/0/foldername".
Anonymous WebDav URLs include "1" path component. For example,
"http://www.yoursite.com/HTCOMNET/hcwebdav/1/7361fc3a/".
These WebDav URLs resemble public links in that they do not require authentication.
The fragment following "1" is a link key authorizing access to the file/folder.
See parameter AnonymousEditingOffice.
net use "*" "http://server-name/link/to/webdav/folder" /savecred /persistent:yes
WebDav over http and https protocols.
Windows WebDav client refuses to authenticate over http protocol when WebDav server uses basic authentication method. You have to use https protocol.
WebDAV Mini Redirector WebDAV client of Windows refuse to authenticate over http protocol when WebDAV server uses basic authentication method. Authentication dialog shows, but client does not send credentials to the server, requests are not sent at all.
WebDav server of HTTP Commander uses Basic authentication in the following cases:
Symptoms:
To enable authentication over http protocol, see Error message when you try to connect to a Windows SharePoint document library... > Workaround > configuring registry.
You need to assign 2 toHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters\BasicAuthLevelregistry value. Value type is DWORD. For changes to take effect, restart the WebClient service or reboot the machine.
https protocol and server certificate
To configure https protocol, the web server should have a valid SSL certificate. You may install self-signed certificate to the server as described in How can I use HTTP Commander with SSL?, deploy custom certification authority in your corporate network, or obtain a certificate from one of the widely known authorities. Note that a self-signed certificate is untrusted by definition, unless you've installed it to the "Trusted Root Certification Authorities" store on each client PC. Connecting to WebDav server over https with invalid certificate is tricky business. Windows Explorer at first refuses to establish the connection at all, it keeps asking for user credentials eventually failing with confusing error message, stating that the web folder is invalid. The other time Windows Explorer connects to a web folder at one dash.
We recommend you to obtain a real certificate from well known authority, or deploy Active Directory Certificate Services if all WebDav clients are bound to internal network.