Hi Tim,

The MultiSitePageNotFoundHandler tries to match a hostname with a node, then checks the "umbracoPageNotFound" property for a redirect nodeId (the 404 page).

The hostname match uses Request.ServerVariables["SERVER_NAME"] ... so thinking this might somehow be an issue?

Can't see anything else in the source-code that might be causing a problem.  If you do find a bug, let me know - we'll patch it up pronto.

Cheers, Lee.

Hiya,

Think I've tracked down the issue. Umbraco doesn't let you specify ports for host names, so if you're running on anything other than port 80, and you've got the site set to append the hostnames to the links, you have to include the port in the domain setting, e.g. www.mysite.com:82, otherwise the links don't work. When the handler checks for the domain, it doesn't include the port, so it doesn't find the root for the domain.

To get round it you could check for a non-standard port and append it on the end of the domain and check for that as well, but to be honest this is probably a pretty rare edge case!

If you do want to add support for this, it's dead easy, just change the line that has:

var domain = HttpContext.Current.Request.ServerVariables["SERVER_NAME"];

to:

var domain = HttpContext.Current.Request.ServerVariables["SERVER_NAME"];

//if there is a port number, append it

var port = HttpContext.Current.Request.ServerVariables["SERVER_PORT"];

if (!string.IsNullOrEmpty(port) && port != "80")
{
domain += ":" + port;
}

Thanks Tim.

Would you mind creating a ticket on our CodePlex please? http://ucomponents.codeplex.com/WorkItem/Create

So that I don't lose track of it.

Cheers, Lee.

Will do!

:)

is working on a reply...