Page not rendering properly when Sharepoint2013 is Accessed via Internet Explorer
book
Article ID: CTX202511
calendar_today
Updated On:
Description
Using IE browser the sharepoint webpage will load partially and multiple browser refresh have to be made to load the contents completely. However, other browsers like Chrome, Firefox is able to load the contents successfully.
Resolution
Refer the 2 screenshot which indicates the difference in HTTP Header size. Increase the MaxHTTPHeader Length in HTTP Profile and bind to the respective Virtual Server (VIP).
Working on Chrome browser:-
Not-Working on IE browser:-
HTTP Profile via GUI:
HTTP Profile via CommandLine:add ns httpProfile new_HTTP_Profile -dropInvalReqs DISABLED -markHttp09Inval DISABLED -markConnReqInval DISABLED -cmpOnPush DISABLED -conMultiplex ENABLED -maxReusePool 0 -dropExtraCRLF ENABLED -incompHdrDelay 7000 -webSocket DISABLED -rtspTunnel DISABLED -reqTimeout 0 -adptTimeout DISABLED -dropExtraData DISABLED -webLog ENABLED -maxReq 0 -persistentETag DISABLED -spdy DISABLED -reusePoolTimeout 0 -maxHeaderLen 30000
Problem Cause
MaxHeaderLength: Number of bytes to be queued to look for complete header before returning error. If complete header is not obtained after queuing these many bytes, request will be marked as invalid and no L7 processing will be done for that TCP connection.IE browser send additional Information / parameters in the Negotiate HTTP Data as compared to the other browsers like Chrome and Firefox. Similarly on Netscaler default limit of MaxHTTPHeader length is 24820bytes (Min = 2048, Max = 61440) this limit has been reached and hence Netscaler is blocking by sending RST.
Additional Information
https://support.microsoft.com/en-us/kb/820129
https://www.iis.net/configreference/system.webserver/security/requestfiltering/requestlimits/headerlimits
http://blogs.technet.com/b/sp/archive/2013/05/29/http-400-bad-request-request-header-too-long-error-in-internet-information-services-iis.aspx
Was this article helpful?
thumb_up
Yes
thumb_down
No