Article ID: 951508 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
Consider the following scenario:
For example, this problem may occur when the following conditions are true:
When ISA Server receives the HTTP 401 status from the Web server, ISA Server returns an "HTTP 302 Redirect" response to the client. This instructs the client to resubmit the request to a different URL. The different URL points to the original URL but with a tag appended onto it. For example, the request to http://domain/test.htm may be redirected to the following appended URL:
http://domain/test.htm&authResendNNNThe "HTTP 302 Redirect" response includes a "Connection: Close" header. Therefore, the client will send the redirected request to ISA over a new session.
When the redirected request reaches ISA Server, the authentication delegation filter identifies the tag and then extracts the original URL. A new authenticated session is opened with the Web server by the delegation filter, and the original URL is sent over this session.
In this scenario, the following problems may occur:
To resolve this problem, apply the hotfix package that is described in the following Microsoft Knowledge Base article:
(https://support.microsoft.com/kb/951510/ )Description of the ISA Server 2006 hotfix package: April 9, 2008
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/824684/LN/ )Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 951508 - Last Review: January 16, 2015 - Revision: 2.0