Known Issues for Reverse Proxies (Windows SharePoint Services 2.0)

  • Article

Because of the way URLs are handled in Microsoft Windows SharePoint Services, no reverse proxy configuration can provide a complete solution. Even after configuring your environment to use either the host-header forwarding or SSL bridging (HTTPS to HTTPS) configuration, you may still experience issues in the following situations:

  • SharePoint Central Administration does not work through a reverse proxy server.

    The instructions in this paper are for the content virtual servers and do not apply to the SharePoint Central Administration site. Any URLs referenced in virtual server management are based on the hostname of the URL used to browse to SharePoint Central Administration, and not on any URLs sent by the reverse proxy server.

  • Administrative e-mail messages from Windows SharePoint Services — such as quota limit warnings and site collection use confirmation e-mail messages — include the URL used when the site was created. This is usually different from the URL sent by the reverse proxy server.

  • To make links in Windows SharePoint Services include HTTPS (instead of HTTP), you must ensure that Microsoft Internet Information Services (IIS) is configured on each virtual server to require SSL. You cannot control this setting from the proxy server. For more information, see "Enabling Secure Sockets Layer (SSL)" in Configuring Authentication (Windows SharePoint Services 2.0) in the Windows SharePoint Services Administrators Guide.

  • The announcement added when you turn on Self-Service Site Creation may not have the correct host header name.

    You can manually edit this announcement on each site that it appears on to include the correct URL.

  • Explorer View, Web Distributed Authoring and Versioning (WebDAV), Web view and Web file properties, the Shared Workspace task pane in Microsoft Office System programs, and opening and saving files from Office programs to the site might fail if ISA Server is configured to intercept HTTP OPTIONS requests.

    You can configure ISA Server 2000 to not intercept these requests by adding a registry key. For more information, see the Knowledge Base article 304340 (https://go.microsoft.com/fwlink/?LinkID=37445\&clcid=0x409).

    HTTP OPTIONS settings are allowed by default for ISA Server 2004.

  • Using the ISA 2004 path-mapping feature to publish Windows SharePoint Services is not supported. Also, Link Translation should be disabled for the ISA 2004 Web Publishing rule when publishing Windows SharePoint Services.

See Also

Concepts

Appendix A: Configuring Certificates from a Commercial Certification Authority (Windows SharePoint Services 2.0)
Appendix B: Setting Up a Local Certification Authority (Windows SharePoint Services 2.0)