Search
Report Types:
Products
Updates
Logs
Bugs
Files
Encounters:
Only Reports that have Encounters
Encounters must contain resolution
Home
Products
Updates
Logs
Bugs
Files
Sign In
Create an Account
Action Links
Create a Product Report
Create a Update/Patch Report
Create a Log/Event Report
Create a Bug Report
Create a File Report
Recent Search Results
No Search results are currently available to display.
Your last search results will be displayed here for the duration of your browser session.
Latest Reports
Mozilla Firefox 3.5
AVIRA AntiVir Premium 9
HP Officejet T series
Cisco IP Phones 7912G
Microsoft Windows Web Server 2008 R2 64-bit
Cisco IP Phones 7925G
HP Photosmart R827
IBM eSeries xSeries 305
Dell PowerEdge R510
HP Photosmart M637
...
11
12
13
14
15
...
Log Report
Print
Edit This Record
Create New
Revision
1
Template
General
Log Name
httperr.log
Type
Error
Source
IIS
Entry ID
400
Average Threat Rating
Average Threat Rating Help
X
Loading...
Encounters
More Info
Related Content
Alert Me
Discuss
Add Your Encounter
Hide Encounters without Resolutions
joverland
Posts: 41
12/21/2010
Revision
4
Threat Rating:
Contains Resolution:
HTTP 400 - Bad Request (Request header too long) is displayed in the browser after accessing an IIS website that uses Windows Integrated Security and the user has a large number of security groups. The number of groups can vary, but you will be at risk with over 100. We have users with over 200 and they all would recieve it if we had not increased the MaxFieldLength and MaxRequestBytes registry settings. Since it was our intranet we set the values to there max limit but you may want to consider something less.
Here are the regisry settings you will need to create to resolve this issue:
HKLM\System\CurrentControlSet\Services\HTTP\Parameters\MaxFieldLength:65534
HKLM\System\CurrentControlSet\Services\HTTP\Parameters\MaxFieldLength:16777216
Both keys are DWORDS and the values are in Decimal units.
IMPORTANT: You must reboot for the settings to take effect. Many hours have been wasted because IISRESET and service restarts do not cut it.
REF:
http://support.microsoft.com/kb/2020943
Peer Reviews (0)
Peer Review Help
X
Loading...
No reviews have been post for this Encounter
Post a Peer Review:
Copyright (c) 2011
About Us
Contact Us
Privacy
Disclaimer
FAQs