Merge pull request #7865 from mszixie/patch-25

AB#3129: Docs 2024 review: Update digest-authentication.md

Author: sevend2

support/developer/webapps/iis/www-authentication-authorization/digest-authentication.md

@@ -1,27 +1,27 @@
 ---
 title: Digest authentication fails
 description: This article provides workarounds for the problem where digest authentication fails when a client sends a request through a proxy to a site IIS using digest authentication.
-ms.date: 04/07/2020
+ms.date: 12/17/2024
 ms.custom: sap:WWW Authentication and Authorization\Digest and advanced digest authentication
 ms.reviewer: atsushin, bariscag
 ---
 # IIS digest doesn't permit pass-though authentication of proxy requests
 
 This article helps you resolve the problem where digest authentication fails when a client sends a request through a proxy to a site and Microsoft Internet Information Services (IIS) uses digest authentication.
 
-_Original product version:_   Internet Information Services 8.5, 8.0  
+_Original product version:_   Internet Information Services  
 _Original KB number:_   3050055
 
 ## Symptoms
 
 Consider the following scenario:
 
 - IIS is configured to use digest authentication.
-- The server receives a request with the via HyperText Transfer Protocol(HTTP) header. (This occurs if the client request is rerouted through a proxy.)
+- The server receives a request with the `Via` HyperText Transfer Protocol (HTTP) header. (This behavior occurs if the client request is rerouted through a proxy.)
 - The resource requested is protected by digest authentication.
 - A child request is created in the IIS pipeline. For example, a request is sent for a directory's default document, and the URL that is sent has a slash (/) as the last character.
 
-In this scenario, digest authentication fails, and the server returns a 401 response.
+In this scenario, digest authentication fails and the server returns a 401 response.
 
 ## Cause