[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1587
  • Last Modified:

Sharepoint-Header is too long (MaxRequestBytes)

Dear all,

 I would like to inquire about the registry parameter (MaxFieldLength-MaxRequestBytes). Currently we have a very large SharePoint farm of 8 servers. Some users of remote locations throws the error "Bad Request - header is too long. "
 Currently we have set the following values:
 MaxFieldLength: 65534
 MaxRequestBytes: 65534

 But some users may receive this error because they belong to many groups and to get the kerberos ticket I believe it is long. The tech people told me that the value (MaxRequestBytes) can not be increased without affecting the infrastructure. I would like to understand why and how it can affect specifically.


I was reading this article: http://support.microsoft.com/kb/2020943
0
Gonzalo Becerra
Asked:
Gonzalo Becerra
  • 3
1 Solution
 
KoenVostersCommented:
Impact:

It will have to  be executed on all the servers of the farm (not the sql server), and you will need to take it up in your upgrade plan of your farm so that if you are adding a webfrontend that you are changing the registry key there as well. If you don't, and you will forget :) ,adding a new frontend will give these users the same error when they are directed to the new frontend by the load balancer.
0
 
Gonzalo BecerraSharePoint - Technical Lead for Operations & Engineering Team - Superrvising AssociateAuthor Commented:
Thanks Kown,

What was to do was change in the 8 servers in the farm, but i recieve this answer: No, because.

 "IMPORTANT: Changing These registry keys Can Be Considered Extremely Dangerous. These larger keys allow HTTP packets to Be Sent to IIS s, which in turn causes May Http.sys to use more memory and May Increase vulnerability to malicious attacks."


 I would like to know as it relates to add this parameter in the registry on all servers in the farm?. Why not raise it above 64k recommend?.

 They are Windows Server 2003 x64 8GB Ram
0
 
Gonzalo BecerraSharePoint - Technical Lead for Operations & Engineering Team - Superrvising AssociateAuthor Commented:
The infrastructure "would suffer"because the one who takes Http.sys Requests to put in a queue that then processes the App Pool ... if you accept headers larger (much larger) memory escalate considerably more, depending on how much it add, which may cause the IIS service fall completely.

 The first request falls into Http.sys, so if you enlarge the size of the header that can be reached, it would be easier to kill the server by sending many large requests (Requests headers large) ... you understand?

 There is more vulnerable the Http.sys, but the infrastructure that would come larger headers ... so mark it in bold, because much will depend on how you calculate it for the header ... it is best to take the header of the friends of Indonesia and see what is the maximum you header is coming, and on that basis to the maximum, ie, be as restrictive as possible.
 Anyway, I recommend that you analyze the log of the server HTTPERR and see if they are well identified any IP they receive that message (in the field s-reason), because of having different IPs to those of Indonesia, without a cause "explained, "is to take care of making this change.
0
 
Gonzalo BecerraSharePoint - Technical Lead for Operations & Engineering Team - Superrvising AssociateAuthor Commented:
I opened a case in Microsoft to ask this issue and this is the response.
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now