Tag: aam
https doesn’t redirect to http in document library MOSS 2007
by mysticslayer on Dec.30, 2008, under MOSS
For a company I work for we have an different kind of situation regards the SharePoint site. We have a DMZ with all the webservers we need. We also got a small MOSS 2007 farm where the company hosts his two SharePoint sites. Both sites are on the same farm and on the intranet it works perfectly.
On of these sites is hosted normally on the http port, and the other on is hosted as an extranet application on the https port. The site hosted on the public http port is good, and doesn’t show any problems.
The certificate for the private site is at the reverse proxy server, although it is also a kind of firewall. We used the technet documentation for implementation (link). We did use the Alternative Access Mappings and we did redirect our https port(proxy) to the http port(Site farm).
Everything works perfectly, except for the Document Library. Normal documents can be opened without any problems, but when you want to access a folder in the document library we got a permission denied error from the proxy server. Why you may ask? Well the document library has folders and show all http:// instead of https://. So it redirects from an secure site into a insecure site were the port is blocked on the DNS.
So we maybe thought that this was related to the firewall instead of SharePoint, well forget that. The problem resists in the Document Library and nothing else. Now we contact Microsoft for this issue, but the problem is that Microsoft has only helpdesk people with knowledge of SharePoint or ISA Server. Microsoft helpdesk wants to relate the problem to the firewall instead of their own product, and I can’t blame them, because it’s their product. Well I’m not happy at all with this, because we won’t change anything in the firewall. We tried everything there is needed to work.
The company were I work for doesn’t have this problem to Exchange Server 2003, and this is the same kind of product, and they have the exact same rules and same implementation… Probably this a bug (or feature) and they can’t solve it… maybe later on…
Well I will keep you informed… when I have a solution my blog will keep you informed about it…
