arnarn - 6:16 pm on Oct 17, 2007 (gmt 0)

We spotted our problem when migrating to a new server last week.

Prior to last week, https: to a non-https (non-secure page) would complete as normal. Ie, the certificate was tied to domain.name, so https://domain.com and [domain.com...] both worked

On our new server, the https is being handled by https://secure.domain.com and any reference of https://domain.com (non-secure) will result in 401.\