NOTE: In IIS 4.0, MaxClientRequestBuffer is only recognized when the program runs on Windows NT 4.0 Server Service Pack 5 or later.
Reason for MaxClientRequestBufferThe MaxClientRequestBuffer registry value was added to IIS as a security measure, so that the maximum size of the request line and header fields could be set by the IIS administrator in order to reduce the likelihood of an attack caused by requests containing large amounts of data in the request line or headers.
NOTE: The HTTP specifications do not specify the maximum size of the request line or header fields.
For more information about a security problem that may occur when very large URLs that contain escape characters are used, see the security bulletin MS00-023 (http://www.microsoft.com/technet/security/bulletin/ms00-023.mspx).
Default Sizes in IIS 4 and 5In IIS 4.0, the default maximum size of request line and header fields is 2 megabytes (MB).
In IIS 5.0, this is reduced to 128 kilobytes (KB).
In IIS 5.0 with Windows 2000 Service Pack 4 installed, this is reduced to 16 KB.
Details of the Request StructureThe data limited by MaxClientRequestBuffer (the response line and headers), consists of all data from the first byte of the request through the last byte before the entity body. This includes the method, the URL, any additional path information, the query string, the HTTP version, all the headers, and the characters that delimit all parts of the request. In other words, this includes all data that is not part of the request's entity body.
Use POST Instead of GET to Send Large Amounts of Data in RequestGET requests use the URL portion of the request line to send information to IIS. The POST method, however, sends the information in the request's entity body instead. Therefore, you should consider using the POST method to send a large amount of data in the request.
MaxClientRequestBuffer Limit Is Affected by BuffersBecause IIS reads the blocks of the request data into buffers, the limit set by MaxClientRequestBuffer is not extremely precise. Therefore, after you use MaxClientRequestBuffer, you may have to test to see if the actual limit on the size of the client request and header fields is what you expect.
Side Effect on SF_STATUS_REQ_READ_NEXTThe use of MaxClientRequestBuffer can affect Internet Server Application Programming Interface (ISAPI) filters. If a filter attempts to use the SF_STATUS_REQ_READ_NEXT feature to read in a complete request before it would normally happen, it can encounter this limit, which causes requests to fail.
For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
Add the MaxClientRequestBuffer Registry ValueImportant This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
To change the maximum size of a URL request, perform the following to add the MaxClientRequestBuffer registry value:
- Run the Registry Editor (Regedt32.exe).
- Locate the following key in the registry:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\w3svc\parameters
- From the Edit menu, select Add Value, and then add the following registry value:Value Name: MaxClientRequestBuffer
Data Type: REG_DWORD
- In the DWORD Editor dialog box, under Radix, select Decimal. In the Data text box, type the number of bytes for the maximum URL request size.
Note You must restart the IIS service for the changes to take effect.
ID d'article : 260694 - Dernière mise à jour : 6 janv. 2009 - Révision : 1