Docs 2024 review: Update http-bad-request-response-kerberos.md

Changing wording of the article to make it clearer where the Kerberos token is sent and correcting some header names.

Author: paulcociuba

support/developer/webapps/iis/www-authentication-authorization/http-bad-request-response-kerberos.md

@@ -7,14 +7,14 @@ ms.reviewer: ivanpash, paulboc
 ---
 # HTTP 400 Bad Request (Request Header too long) responses to HTTP requests
 
-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. 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 contains a Kerberos authentication ticket is sent to a website that's hosted on Internet Information Services (IIS) and is configured to use Windows Integrated Authentication authentication, the HTTP request header can have a considerable lenght that exceeds the maximum size for such headers accepted by the IIS server by default. This article helps you work around the HTTP 400 error that occurs when the HTTP request header is too long.
 
 _Original product version:_   Windows Server 2016  
 _Original KB number:_   2020943
 
 ## Symptoms
 
-An HTTP request that needs Kerberos authentication is sent from a browser to a website that's hosted on IIS. The website is configured to use Kerberos authentication. However, instead of receiving the expected webpage, you receive an error message that resembles the following one:
+When attempting to access a web-application hosted on IIS (Internet Information Services) that requires Windows Integrated Authentication to grant users access to its resources, the client (browser) will submit an HTTP request that comports an authentication header (header name: Authorization) which will use either NTLM or Kerberos as authentication protocols. In the scenario in which a Kerberos authentication token is sent from a browser to a website that's hosted on IIS, instead of receiving the expected webpage, you receive an error message that resembles the following one:
 
 > HTTP 400 - Bad Request (Request header too long)
 
@@ -24,29 +24,31 @@ This response could be generated by any HTTP request that includes Windows Remot
 
 This issue may occur if the user is a member of many Active Directory user groups.
 
-The HTTP request to the server contains the Kerberos token in the `WWW-Authenticate` header. The header size increases together with the number of user groups. If the HTTP header or packet size increases past the limits that are configured on the server, the server may reject the request and send an error message as the response.
+The HTTP request to the server contains the Kerberos token in the `Authorize` header. The size of the Kerberos token contained within the HTTP header increases together with the number of user groups for the authenticating user. If the HTTP header or packet size increases past the limits that are configured on the server, the server may reject the request and send an error message as the response.
 
 ## Workaround 1: Decrease the number of Active Directory groups
 
 Decrease the number of Active Directory groups that the user is a member of.
 
 ## Workaround 2: Set MaxFieldLength and MaxRequestBytes registry entries
 
-Increase the settings for the `MaxFieldLength` and the `MaxRequestBytes` registry entries on the server so that the user's request headers don't exceed these values. To determine the appropriate settings, use the following calculations:
+Increase the settings for the `MaxFieldLength` and the `MaxRequestBytes` registry entries on the IIS server so that the user's request headers don't exceed these values. To determine the appropriate settings, use the following calculations:
 
 1. Calculate the size of the user's Kerberos token by using the formula described in [Problems with Kerberos authentication when a user belongs to many groups](../../../../windows-server/windows-security/kerberos-authentication-problems-if-user-belongs-to-groups.md).
 
 2. Set the value of `MaxFieldLength` and `MaxRequestBytes` on the server to 4/3 * T bytes, where T is the user's token size in bytes. HTTP encodes the Kerberos token by using base64 encoding.
 
    > [!NOTE]
-   > This replaces every three bytes in the token with four base64-encoded bytes. Changes that are made to the registry do not take effect until you restart the HTTP service. Additionally, you may have to restart any related services, such as IIS services.
+   > This replaces every three bytes in the token with four base64-encoded bytes. Changes that are made to the registry do not take effect until you restart the HTTP service. Additionally, you will need to restart any related services, such as IIS services.
 
 Depending on your application environment, you might also work around this problem by configuring the website to use Windows NT LAN Manager (NTLM) instead of Kerberos. Some application environments require Kerberos authentication to be used for delegation. We consider Kerberos authentication to be more secure than NTLM. And we recommend that you don't disable Kerberos authentication before you consider the security and delegation ramifications.
 
 ## More information
 
 By default, there is no `MaxFieldLength` registry entry. This entry specifies the maximum size limit of each HTTP request header. The `MaxRequestBytes` registry entry specifies the upper limit for the total size of the Request line and the headers. Typically, this registry entry is configured together with the `MaxRequestBytes` registry entry. If the `MaxRequestBytes` value is lower than the `MaxFieldLength` value, the `MaxFieldLength` value is adjusted. In large Active Directory environments, users may experience logon failures if the values for both these entries aren't set to a sufficiently high value.
 
+The size of the `MaxFieldLength` and `MaxRequestBytes` should not exceed the maximum allowed values for these fields which are defined [here](https://learn.microsoft.com/en-us/troubleshoot/developer/webapps/iis/health-diagnostic-performance/httpsys-registry-windows) 
+
 For IIS versions shipped with Windows Server 2016 and later, the `MaxFieldLength` and `MaxRequestBytes` registry keys are located in the following subkey:  
 
 `HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\HTTP\Parameters`