Microsoft Knowledge Base Email Alertz

(840931) - Discusses an issue where you cannot connect to the SharePoint Portal Server portal site if you use Apache Web server to reverse-proxy Windows SharePoint Services.

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 840931 - Last Review: October 18, 2007 - Revision: 3.1

"The page cannot be displayed" error message when you connect to the portal site if you use Apache Web server to reverse-proxy Windows SharePoint Services 2.0

SYMPTOMS

When you use an Apache Web server to reverse-proxy Microsoft Windows SharePoint Services 2.0 or Microsoft Office SharePoint Portal Server 2003, you may find that you cannot connect to the SharePoint sites with Microsoft Internet Explorer when you use the following URL:
http://ServerName
When you try to do so, you receive the following error message:
The page cannot be displayed

CAUSE

This problem occurs because Windows SharePoint Services 2.0 and SharePoint Portal Server 2003 incorrectly process the response to the client request. When you connect to the portal site, Apache tries to connect to the Windows SharePoint Services 2.0 Web site or to the SharePoint Portal Server 2003 Web site to proxy the data. Windows SharePoint Services 2.0 and SharePoint Portal Server 2003 do not include a reason phrase or a trailing space in the "302 Object Found" response that is returned to the Apache Web server. This condition causes the Apache Web server to incorrectly process the response from Windows SharePoint Services 2.0 or SharePoint Portal Server 2003 and as a result, the client receives the error message that is mentioned in the "Symptoms" section.

WORKAROUND

To work around this problem, use the following URL to connect to the portal site:
http://ServerName/default.aspx

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For more information about how to configure and administer Windows SharePoint Services 2.0, see the Microsoft Windows SharePoint Services Administrator's Guide. To view the Microsoft Windows SharePoint Services 2.0 Administrator's Guide, visit the following Microsoft Web site:
http://www.microsoft.com/downloads/details.aspx?familyid=A637EFF6-8224-4B19-A6A4-3E33FA13D230 (http://www.microsoft.com/downloads/details.aspx?familyid=A637EFF6-8224-4B19-A6A4-3E33FA13D230)
For more information about Windows SharePoint Services 2.0, visit the following Microsoft Web site:
http://technet.microsoft.com/en-us/windowsserver/sharepoint/bb267377.aspx (http://technet.microsoft.com/en-us/windowsserver/sharepoint/bb267377.aspx)

For more information about Microsoft Office SharePoint Portal Server 2003, visit the following Microsoft Web site:
http://office.microsoft.com/en-us/sharepointserver/FX101494611033.aspx (http://office.microsoft.com/en-us/sharepointserver/FX101494611033.aspx)
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.

APPLIES TO
  • Microsoft Windows SharePoint Services 2.0
  • Microsoft Office SharePoint Portal Server 2003
Keywords: 
kberrmsg kbbug kbnofix KB840931
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate

LanceVD - www.LinxSD.com Report As Irrelevant  
Written: 11/2/2004 7:04 PM
Although not totally related... Problem: I use SQUID proxy daemon, implented as a Group Policy, and LAN users were receiving an 'access denied' message when browsing to our SharePoint server using its FQDN. Resolution: I set the GPO IE Proxy Exceptions setting to bypass the FQDN of our SharePoint server (we use SPS with the same FQDN internally & externally, but our internal DNS points to our private address space). Results: All joy now.

Dchan - dchan17 NOSPAM-AT-NOSPAM gmail.com Report As Irrelevant  
Written: 5/12/2006 9:37 PM
Somewhat related... SPS2003 with the same FQDN internally and externally, but it will prompt for login internally as well.. how do I resolve