People Search Result URL Shows ":80" Suffix for HTTPS

Situation

There is a MOSS 2007 farm with Shared Service provider configured to use mysites.domain.com as a My Sites host Web site.
Two Alternate Access Mappings were created for My Sites Web site:

Default Zone: http://mysites.domain.com

Extranet Zone: https://mysites.domain.com

In IIS this is a single Web site with aditional binding for https on port 443.

If you search for people using Extranet Zone mapping for the SharePoint Web site in the search result the URL is https://mysites.domain.com:

After installation of Infrastructure Update for Microsoft Office Servers search result Web site URL for people looks like https://mysites.domain.com:80 which is wrong, because there is no Web site on port 80 available using https:

Some ideas are explained in the following article:

People Search Results adds a :80 Suffix to results on an External Facing Site

And cosmetic workaround is provided in the following article:

How to remove something (the port) from the URL as returned in the search results (searchresults.aspx)

The problem with the above workarounds is that it only patches certain areas, but not the cause of the issue. I.e. if you just change the Search Result Web part for people doesn't mean you don't need to change this URL everywhere on your Web site you display a user.

I'm in the process of resolving this issue.

Stay tuned.

Comments

Setting up External Content Type for SQL Server database using SQL Server authentication - SharePoint 2010 Foundation

This post is a follow up on the issues that I have got setting up External Content Type (ECT) on SharePoint 2010 Foundation that was going to connect to remote SQL Server database for information. I cannot use my SharePoint user accounts to access SQL Server. According to the information I have discovered ECT and Business Connectivity Services are available in the SharePoint 2010 Foundation, but there are some issues if you want to use authentication methods in your external connections that are different from Windows Identity or Current User Identity. This is because there is no Secure Store Service in SharePoint 2010 Foundation which serves as an impersonation hub and is only available in SharePoint 2010 Server edition. The issues are coming from the fact that you can actually create ECT in SharePoint Designer 2010 providing just Secure Store ID and system would ask you for credentials and here you go, but when you try to use your ECT in External Lists or as a lookup columns you w...

Document Sets - SharePoint 2010 - Part 1

Hi again, in this post I am going to demonstrate how set up and start using Document Sets in SharePoint 2010. In Beta version there was a little problem when working with Document Sets. You could see the discussion around it here: Document Set content type issue . Now it is fixed and I will show you how to set up Document Sets properly to also use Keywords. 1. Activate two site collection features - Document Sets and Document ID Service: 2. Select a document library settings where you want to implement Document Sets. In my case it is Shared Documents. When you have selected the settings go to Advanced settings and then allow content types management: 3. Add an existing content type called Document Set: 4. Now I want to create a new Document Set. I have a sales opportunity and I have two documents related to this sales opportunity. So first I select New Document -> Document Set command, then provide name and description and there it is: 5. To check if our Document ID...

Version control in Office 365

When working with documents in SharePoint or Office 365, quite often files are named like "Project-Budget-Report-v1.55", "Project-Budget-Report-v1.56", "Project-Budget-Report-v2.0" etc. and stored in the same folder or library. This is to achieve version control from the user perspective. This is not a good idea for the following reasons: Storing redundant information Confusion which version to use when Browsing though many documents to see what information/metadata changed if required Version numbering should be automated, no time spent by the document author There is a better way to manage versions of documents and to use tools already available to us in Office 365. File name should not contain the version number in it. Every time you upload a document with the same name the SharePoint will increment the version number for you automatically in the current set up of our Office 365 site we use for customer documentation. Then to manage the...

SharePoint etc.

Search This Blog