You connect a Distributed Authoring and Versioning (DAV) share from a computer that is running Windows 8.1, Windows Server 2012 R2, Windows 7 Service Pack 1, or Windows Server 2008 R2 Service Pack 1. The DAV share may be hosted on an instance of SAP NetWeaver Application Server, for example. When you use "Basic authentication" to connect to the DAV share through the Internet, you may be unable to open links from WebDAV servers in Internet Explorer. Additionally, you receive an error message that resembles the following:
Picture one: Internet Explorer could not open http://DAVserver:5300/folder1/folder2/folder3/ as a web Folder. Would you like to see its default view instead?
Note In this error message, the DAV share is enabled only on the third folder.
This problem occurs because of incorrect behavior when the URL name is parsed.
To resolve this issue in Windows 8.1 and Windows Server 2012 R2, install update 2919355. To resolve this issue in Windows 7 and Windows Server 2008 R2, install the hotfix that is described in this article.
Update information for Windows 8.1 and Windows Server 2012 R2
For more information about how to obtain update 2919355, click the following article number to view the article in the Microsoft Knowledge Base:
2919355 Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 Update April, 2014
Hotfix information for Windows 7 and Windows Server 2008 R2
A supported hotfix is available from Microsoft Support. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, go to the following Microsoft website:
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any previously released hotfix.
The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows 7 and Windows Server 2008 R2 file information and notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
6.1.760 1. 22xxx
Windows 7 and Windows Server 2008 R2
GDR service branches contain only those fixes that are widely released to address widespread, extremely important issues. LDR service branches contain hotfixes in addition to widely released fixes.
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows 7 and Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 7
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Additional file information
Additional file information for Windows 7 and for Windows Server 2008 R2
Additional files for all supported x86-based versions of Windows 7
In Windows XP, Microsoft Office installed its own WebDAV extension. This extension was not a redirector and is not comparable to the integrated DAV redirector in Windows 7. Both Windows XP and Windows 7 use an integrated DAV redirector caching mechanism. This mechanism makes sure that you do not have to provide your credentials every time that you map a DAV share. To clear this cache, restart the Webclient service.
This caching mechanism may be a perceived security issue. In our view, this is not a security issue because you should typically log off or lock your session when you are away from the computer.
See the terminology that Microsoft uses to describe software updates.
Third-party information disclaimer
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.