A "200" HTTP status code is incorrectly logged in the IIS log when a partial content client request succeeds in IIS 7.5 in Windows 7 or in Windows Server 2008 R2

Applies to: Internet Information Services 7.5Windows 7Windows Server 2008 R2

Symptoms


Consider the following scenario:
  • You install Internet Information Services (IIS) 7.5 on a computer that is running Windows 7 or Windows Server 2008 R2.
  • This computer hosts a large file on an IIS website.
  • You download the file partly from a client computer by sending some byte-range requests to the computer that is running IIS.
In this scenario, a 200 HTTP status code is incorrectly logged in the IIS log file after the download succeeds. However, the correct HTTP status code that should be logged is 206. 206 indicates the client request for partial content succeeds. Therefore, you may be unable to track download activity on the computer correctly.

Note This issue does not occur in IIS 6 and in IIS 7.

Cause


This issue occurs because of an error in the HTTP.sys file.

Resolution


Hotfix information

A supported hotfix is available from Microsoft. 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, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running Windows 7 or Windows Server 2008 R2.

Registry information

To use the hotfix, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global 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 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 MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2 and for Windows 7" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. 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
File nameFile versionFile sizeDateTimePlatform
Http.sys6.1.7600.20715514,04819-May-201008:15x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Http.sys6.1.7600.20715750,08019-May-201008:23x64
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Http.sys6.1.7600.207151,442,30419-May-201007:42IA-64

Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information


For more information about the HTTP status codes in IIS 7.0, click the following article number to view the article in the Microsoft Knowledge Base:

943891 The HTTP status codes in IIS 7.0

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

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
File namePackage_1_for_kb2078804~31bf3856ad364e35~x86~~6.1.1.0.mum
File versionNot applicable
File size1,820
Date (UTC)20-May-2010
Time (UTC)00:52
PlatformNot applicable
File namePackage_2_for_kb2078804~31bf3856ad364e35~x86~~6.1.1.0.mum
File versionNot applicable
File size1,800
Date (UTC)20-May-2010
Time (UTC)00:52
PlatformNot applicable
File namePackage_for_kb2078804_rtm~31bf3856ad364e35~x86~~6.1.1.0.mum
File versionNot applicable
File size1,940
Date (UTC)20-May-2010
Time (UTC)00:52
PlatformNot applicable
File nameX86_82d53a450141b2a3b853f323ac9e974f_31bf3856ad364e35_6.1.7600.20715_none_9fef16810ee20c08.manifest
File versionNot applicable
File size692
Date (UTC)20-May-2010
Time (UTC)00:52
PlatformNot applicable
File nameX86_microsoft-windows-http_31bf3856ad364e35_6.1.7600.20715_none_ad6ca45d93135631.manifest
File versionNot applicable
File size175,661
Date (UTC)19-May-2010
Time (UTC)17:17
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameAmd64_221fa13f5910a974cfdd1728fdad9ee7_31bf3856ad364e35_6.1.7600.20715_none_c4ded3f6d4508950.manifest
File versionNot applicable
File size696
Date (UTC)20-May-2010
Time (UTC)00:52
PlatformNot applicable
File nameAmd64_microsoft-windows-http_31bf3856ad364e35_6.1.7600.20715_none_098b3fe14b70c767.manifest
File versionNot applicable
File size175,667
Date (UTC)19-May-2010
Time (UTC)16:24
PlatformNot applicable
File namePackage_1_for_kb2078804~31bf3856ad364e35~amd64~~6.1.1.0.mum
File versionNot applicable
File size2,052
Date (UTC)20-May-2010
Time (UTC)00:52
PlatformNot applicable
File namePackage_2_for_kb2078804~31bf3856ad364e35~amd64~~6.1.1.0.mum
File versionNot applicable
File size1,810
Date (UTC)20-May-2010
Time (UTC)00:52
PlatformNot applicable
File namePackage_for_kb2078804_rtm~31bf3856ad364e35~amd64~~6.1.1.0.mum
File versionNot applicable
File size2,174
Date (UTC)20-May-2010
Time (UTC)00:52
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File nameIa64_f8c8017ce8bd376d123c9e545fda45b0_31bf3856ad364e35_6.1.7600.20715_none_11c781f8963cb706.manifest
File versionNot applicable
File size694
Date (UTC)20-May-2010
Time (UTC)00:52
PlatformNot applicable
File nameIa64_microsoft-windows-http_31bf3856ad364e35_6.1.7600.20715_none_ad6e485393115f2d.manifest
File versionNot applicable
File size175,664
Date (UTC)19-May-2010
Time (UTC)16:22
PlatformNot applicable
File namePackage_1_for_kb2078804~31bf3856ad364e35~ia64~~6.1.1.0.mum
File versionNot applicable
File size2,046
Date (UTC)20-May-2010
Time (UTC)00:52
PlatformNot applicable
File namePackage_for_kb2078804_rtm~31bf3856ad364e35~ia64~~6.1.1.0.mum
File versionNot applicable
File size1,689
Date (UTC)20-May-2010
Time (UTC)00:52
PlatformNot applicable