Microsoft KB Archive/823099

= Extra CRLF Character Is Added to a POST Request That Is Sent to an HTTP 1.1 Server =

Article ID: 823099

Article Last Modified on 11/15/2007

-

APPLIES TO

 Microsoft Internet Explorer 6.0, when used with:  Microsoft Windows 98 Standard Edition

 Microsoft Windows 98 Second Edition

 Microsoft Windows Millennium Edition

 Microsoft Windows NT 4.0</li></ul>

 Microsoft Windows XP Professional</li></ul>

 </li></ul> </li></ul>

-

<div class="notice_section">

<div class="symptoms_section">

SYMPTOMS
When a POST request is sent to a HTTP 1.1 server, Internet Explorer may append an extra carriage return and line feed character (CRLF) to the end of the post. This may cause problems with the server. The network may stop responding (hang) or you may receive a &quot;Page Not Found&quot; error message, depending on how the server or the Web application is configured.

Note If you suspect that you have this problem, follow the steps in the &quot;Steps to Reproduce the Problem&quot; section to test the problem. If you have this problem, apply the fix that is listed in the &quot;Resolution&quot; section.

<div class="cause_section">

CAUSE
This problem occurs because Internet Explorer may incorrectly store gzip compressed pages with the HTTP 1.0 header. If that page is later requested by Internet Explorer, it will read the 1.0 header and it will think that it should send an extra CRLF (in a subsequent POST request). Internet Explorer typically sends an extra CRLF in a POST request when it thinks that it is communicating with an HTTP 1.0-based server.

<div class="resolution_section">

RESOLUTION
A supported hotfix is now 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 this specific problem. This hotfix might 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, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

The English version of this fix has the file attributes (or later) 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 tool in Control Panel. <pre class="fixed_text">  Date         Time   Version        Size     File name --  26-Jun-2003  16:07  6.0.2800.1220  483,840  Urlmon.dll

<div class="workaround_section">

WORKAROUND
To work around this problem, change the SendExtraCRLF setting in the registry. To do this, follow these steps: <ol> Click Start, and then click Run.</li> In the Open box, type Regedit, and then click OK.</li> Locate, and then click the following key in the registry:

</li> On the Edit menu, point to New, and then click DWORD Value.</li> Type SendExtraCRLF, and then press ENTER.</li> With SendExtraCRLF selected, click Modify on the Edit menu.</li> In the Value data box, type 0, and then click OK.</li></ol>

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

<div class="securedata_section">

Steps to Reproduce the Problem
<ol>  Create a test page containing a form. For example, type the following HTML code in Notepad: <a href=&quot;test.htm&quot;>Test</a> <form action=&quot;bogus.asp&quot; method=&quot;post&quot;> <input type=&quot;text&quot; name=&quot;val1&quot;> <input type=&quot;submit&quot;> </li> On the File menu, click Save to save the test form on your Internet Information Server (IIS) with HTTP compression turned on.</li> Start a Network Monitor trace.</li> Locate your test form.</li> Locate test form again using the link.</li> <li>Submit the form to perform a post operation. The destination URL does not exist and you will receive an error. This is expected.</li> <li>Stop the Network Monitor trace.</li> <li>Look in the Network Monitor trace.</li></ol>

Result: The POST operation should contain an extra CRLF in the post data even though the connection is with an HTTP 1.1 server. There should also be a GET request for the test form the second time and it should have responded with Not Modified (or the GET for the test form for the second occurrence may not even exist).

Keywords: kbhotfixserver kbqfe kbqfe kbie600sp2fix kbie600presp2fix kbfix kbbug KB823099

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.