Microsoft Knowledge Base Email Alertz

KBAlertz.com: FIX: IIS 6.0 may close a connection unexpectedly when a client application sends approximately 4,000 POST requests by using chunked transfer encoding on the same HTTP connection

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]

Search KbAlertz

Advanced Search

Webmasters
Put kbAlertz on your website.
[ Click Here for more! ]





ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
KBAlertz referrals get
** SIX MONTHS FREE **


Community Site



We Send hundreds of thousands of emails using ASP.NET Email


ASP.NET 3.5 Web Hosting with Windows 2008 and SQL 2008: Click Here!
Discount ASP.NET Hosting
ASP.NET 2.0 and 3.5
Windows2008 and SQL2008
US and UK Hosting
KBAlertz referrals get
** SIX MONTHS FREE **




Mentioned In








Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks




Article ID: 967853 - Last Review: April 23, 2009 - Revision: 2.0

FIX: IIS 6.0 may close a connection unexpectedly when a client application sends approximately 4,000 POST requests by using chunked transfer encoding on the same HTTP connection

Hotfix download is availableHotfix Download Available
View and request hotfix downloads

On This Page

SYMPTOMS

Consider the following scenario:
  • A client application sends approximately 4,000 POST requests to a server that is running Internet Information Services (IIS) 6.0.
  • The client application sends the POST requests by using chunked transfer encoding on the same HTTP connection.
  • The HTTP Keep-Alives feature is enabled on the server that is running IIS 6.0.
In this scenario, IIS 6.0 may close the connection unexpectedly by sending TCP RESET packets to the client application. Additionally, you may see a Timer_HeaderWait error in the HTTPERR#.log file. The log entry may resemble the following:
#Date: <Date> <Time>
#Fields: date time c-ip c-port s-ip s-port cs-version cs-method cs-uri sc-status s-siteid s-reason s-queuename
<Date> <Time> <Client IP> <Client Port> <Server IP> <Server Port> - - - - - Timer_HeaderWait
Note The HTTPERR#.log file is used for HTTP.sys error logging. By default, this file is located in the following directory:
%WinDir%\system32\LogFiles\HTTPERR

CAUSE

This issue occurs because of a code defect in the HTTP kernel-mode driver (HTTP.sys) that occurs when the HTTP kernel-mode driver parses the POST requests that are sent by using chunked transfer encoding.

RESOLUTION

Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

You must have Windows Server 2003 Service Pack 2 (SP2) installed to apply this hotfix.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
x86
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Http.sys5.2.3790.4472293,88806-Mar-200911:50x86
x64
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Http.sys5.2.3790.4472565,24806-Mar-200912:48x64
IA-64
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Http.sys5.2.3790.4472811,00806-Mar-200912:44IA-64

WORKAROUND

To work around this problem if you cannot apply this hotfix, do not use chunked transfer encoding in POST requests from the client application. Instead, use the Content-Length entity-header field.

For more information about the Content-Length entity-header field, see section 14.13 of RFC 2616. To do this, visit the following World Wide Web Consortium (W3C) Web site:
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html (http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html)
Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.

STATUS

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

MORE INFORMATION

For more information about chunked transfer encoding, see section 3.6 of RFC 2616. To do this, visit the following World Wide Web Consortium (W3C) Web site:
http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html (http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html)
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684  (http://kbalertz.com/Feedback.aspx?kbNumber=824684/ ) Description of the standard terminology that is used to describe Microsoft software updates

APPLIES TO
  • Microsoft Internet Information Services 6.0
Keywords: 
kbhotfixserver kbautohotfix kbexpertiseinter kbexpertiseadvanced kbqfe kbsurveynew KB967853
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

Be the first to leave feedback, to help others about this knowledge base article.

(Optional) Name

(Optional) Public URL Or Email

Comments
No HTML -- Text Only Please