Article ID: 917051 - View products that this article applies to.
When you use overlapped HTTP protocols on a Microsoft Internet Security and Acceleration (ISA) Server 2004 computer, you may find that the Web Proxy Filter logs requests that have incorrect references. For example, the Web Proxy Filter may log requests that have references to the default access rule instead of to the access rule that is configured to enable HTTP protocols.
Note When you use overlapped HTTP protocols in ISA Server 2004 Enterprise Edition-based computers, the requests that are logged may have references to the Enterprise default rule.
This problem may occur because the Web Proxy Filter in ISA Server 2004 incorrectly sets the logging field to the last rule that is processed. This typically occurs when multiple definitions exist for the same port.
A fix is available for computers that are running ISA Server 2004 Service Pack 2 (SP2). To resolve this problem, install the hotfix that is described in the following Microsoft Knowledge Base article:
(http://support.microsoft.com/kb/916106/ )Update for HTTP issues in Internet Security and Acceleration Server 2004 Service Pack 2
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Overlapped HTTP protocols are used when you have to prevent the Web Proxy Filter from intercepting the Web traffic. This configuration may be required when non-standard HTTP traffic uses TCP port 80. If you use the standard HTTP protocol, the traffic may be denied if it does not comply with the RFC standard.
To enable non-standard HTTP traffic in this scenario, the custom HTTP definition must not be bound to the Web Proxy Filter.
To use overlapped HTTP protocols, you must deny the HTTP protocol for sites where a custom HTTP protocol is used. This is to make sure that ISA Server 2004 chooses the correct protocol.
For example, if a virtual private network (VPN) client has to use the custom HTTP protocol to connect to an internal server, the rule that enables the custom HTTP protocol must have a higher priority than the rule that enables the standard HTTP protocol. You must also configure a rule to deny the standard HTTP protocol to the internal server to make sure that the custom HTTP protocol is used.
The following table lists the rules that have to be configured to enable traffic in this scenario:
Collapse this tableExpand this table
Article ID: 917051 - Last Review: December 4, 2007 - Revision: 2.3
Contact us for more help
Connect with Answer Desk for expert help.