WSS 3.0 SP2 and reverse proxy issue
Hi everyone,
Given the following configuration:
WSS 3.0 Site, extended to two zones:
http://<internal name>/ - Default Zone with Windows Integrated Security
http://<internal name>:81/ - Extranet Zone with FBA
Works like a charm. Now, the FBA based Zone shall be provided by means of a
reverse proxy. This proxy is a 3rd party product and configured as follows:
https://<external name>/ is forwarded to http://<internal name>:81/
Client request are not altered in any way.
No link rewriting
The strange issue is now that links are scrambled as follows:
From the client perspective using the
https://<external name>/
URL, links are returned as
http://<external name>:81/
So a mixture of both external and internal.
The alternate access mappings for the intranet zone is configured as:
Internal URL Zone External URL
http://<internal name>:81/ Extranet https://<external name>/
http://<external name>/ Extranet https://<external name>/
Can anyone give me an enlightment on this?
Thanks everyone,
Regards
Joerg Fischer
Jrg Fischer
July 12th, 2010 6:22pm
Start with this link on using the IISlogs to troubleshoot this.
The title seems a little off topic but the troubleshooting steps will help.
http://support.microsoft.com/kb/2000283
This blog elaborates a bit more on it
http://blogs.msdn.com/b/rodneyviana/archive/2009/06/24/blobcache-will-not-work-if-the-request-url-is-not-in-the-alternate-access-mapping-list.aspx
Also take a look at
http://blogs.msdn.com/b/sharepoint/archive/2007/03/06/what-every-sharepoint-administrator-needs-to-know-about-alternate-access-mappings-part-1.aspxFred Ellis - MSFT
Free Windows Admin Tool Kit Click here and download it now
July 20th, 2010 6:52pm