Article ID: 975525 - View products that this article applies to.
All HTTP requests that are sent to a service that is hosted in Microsoft Windows Azure pass through a load balancer. The load balancer redirects each incoming request to one of several identical nodes in the Windows Azure subnet. Each node runs an instance of the service on an arbitrary port. The arbitrary port is not the real port that receives the request. For example, you send a request to the following URL:
http://myapp.cloudapp.net:80The load balancer redirects this request to a node that resembles the following:
http://internalazurenode:20000Windows Azure has a feature that rewrites the SERVER_PORT variable by using the port number from the HTTP_HOST variable. Then, you can get the public URL of the current service by checking the HttpContext.Current.Request.Url variable. However, the WCF service that uses the Microsoft .NET Framework 3.5 does not support this feature. Therefore, the service fails when it calls the Lookup method.
This hotfix updates the transport manager and the endpoint message filter so that they ignore the port information. This behavior enables the WCF service to support the Windows Azure feature that rewrites the SERVER_PORT variable.
Windows Vista and Windows Server 2008To resolve this problem in Windows Vista or in Windows Server 2008, download and apply the hotfix that is described in Microsoft Knowledge Base article 981001. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/981001/ )A hotfix rollup is available for Windows Communication Foundation in the .NET Framework 3.5 SP1 for Windows Vista SP2 and Windows Server 2008 SP2
Windows 7 and Windows Server 2008 R2To resolve this problem in Windows 7 or in Windows Server 2008 R2, download and apply the hotfix that is described in Microsoft Knowledge Base article 981002. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/981002/ )A hotfix rollup is available for Windows Communication Foundation in the .NET Framework 3.5 SP1 for Windows 7 and Windows Server 2008 R2
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.