
This response could be generated by any HTTP request that includes Windows Remote Management (WinRM).

HTTP 400 - Bad Request (Request header too long) However, instead of receiving the expected webpage, you receive an error message that resembles the following one: The website is configured to use Kerberos authentication. Original product version: Windows Server 2016 Original KB number: 2020943 SymptomsĪn HTTP request that needs Kerberos authentication is sent from a browser to a website that's hosted on IIS. This article helps you work around the HTTP 400 error that occurs when the HTTP request header is too long.


When an HTTP request that needs Kerberos authentication is sent to a website that's hosted on Internet Information Services (IIS) and is configured to use Kerberos authentication, the HTTP request header would be very long.
