This article was previously published under Q305314
This article has been archived. It is offered "as is" and will no longer be updated.
Clients may not be able to use Web browsers to gain access to Web programs that you uploaded if:
You uploaded the Web programs to a server other than the default virtual Hypertext Transfer Protocol (HTTP) server.-and-
The client tries to access them through a connection that is secured by using Secure Sockets Layer (SSL).
The client displays HTTP server error message 500.100:
Bind to session failed for 'http://url/indexpage-new.htm', hr=0x80040e19.
Beginning in Exchange Server 2000 Service Pack 1 (SP1), Exchange 2000 provides support for uploading Web programs to the server. You can do so by using the Application Deployment Wizard from the Web Storage System software development kit (SDK).
When an SSL-secured connection is established between an HTTP client and server, only the server's Internet Protocol (IP) address and port number are available to identify the server unambiguously. A host header is not helpful in this situation. For additional information about why a host header is not helpful in this situation, click the article number below to view the article in the Microsoft Knowledge Base:
187504 HTTP 1.1 Host Headers Are Not Supported When You Use SSL
The host header is transmitted in SSL-encrypted form from the client to the server so that the host header cannot be used to identify the server to which the SSL decryption key is bound.
To resolve this problem, obtain the latest service pack for Microsoft Exchange 2000 Server. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
301378 XGEN: How to Obtain the Latest Exchange 2000 Server Service Pack
The English version of this fix should have the following file attributes or later:
NOTE: Because of file dependencies, this update requires Microsoft Exchange Server 2000 Service Pack 1.
Microsoft has confirmed that this is a problem in Microsoft Exchange 2000 Server. This problem was first corrected in Microsoft Exchange 2000 Server Service Pack 2.
Distribute the server functionality to a front end-end server and back-end server configuration. In this configuration the browser gains access to the front-end server is accessed, and the front-end server decrypts the SSL-encrypted information that the front-end server receives from the client. The SSL-certificate is bound to the IP address of the front-end server, instead of the secondary IP address of the back-end server. This way, the back-end server only has to deal with information that is already decrypted, which the back-end server can associate with a host header.
Integrated Windows Authentication is not available for front-end server and back-end server configurations.