CRS: Replication Through a Proxy Server Fails Using FTP and HTTP

• Microsoft Commercial Internet System, version 1.0

SYMPTOMS

The Content Replication System (CRS) fails to replicate from an FTP and an HTTP URL when a proxy server is required.

CAUSE

When a proxy is selected for a CRS project, CRS must specify the proxy using the Windows Internet API (Wininet.dll).

In Microsoft Commercial Internet System (MCIS) version 1.0, you can use either of two different methods to specify a proxy using the Wininet.dll file.

However, the Wininet.dll file was updated in Microsoft Internet Explorer version 3.02 so that only one supported method to specify a proxy exists. CRS 1.0 does not use the currently supported method for specifying a proxy, which causes the proxy setting to fail.

RESOLUTION

The Crsdll.dll file was modified to use the supported method for specifying the proxy in the Wininet.dll file. This change requires Internet Explorer version 3.02 to allow it to work correctly for the updated Wininet.dll file.

NOTE: This hotfix has a known limitation: You cannot run an HTTP pull simultaneously with an FTP pull if they are both going through proxies.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Commercial Internet System, version 1.0. A supported fix is now available, but is not fully regression-tested and should be applied only to systems experiencing this specific problem. Unless you are severely impacted by this specific problem, Microsoft recommends that you wait for the next Service Pack that contains this fix. Contact Microsoft Technical Support for more information.

Keywords          : kbother
Version           : 1.0
Platform          : winnt
Hardware          : ALPHA x86
Issue type        : kbbug
Solution Type     : kbfix