What Sitefinity does is switching the protocol depending on whether you have SSL or not for a given page. If the certificate is not valid this should not cause 404.
Each page has a property RequireSSL . If this property is set to true the page will open under SSL.
When "Require SSL" is set to No the request is processed to the HTTP port.
Inside <cms> node of website config file you could try adding =the following parameters that affect the SSL redirection.
- ToHttpsOnly redirects only to HTTPS if RequireSSL is true.
- None - no redirection regardless of the RequireSSL page property
- this is the default value
- redirects in both directions regarding the RequireSSL
Most probably there is some redirect that breaks the behavior of the aliased domain name.
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Public Issue Tracking
system and vote to affect the priority of the items