+1-888-365-2779
Try Now
More in this section

Forums / General Discussions / page not found when Require SSL set

page not found when Require SSL set

5 posts, 0 answered
  1. Jason
    Jason avatar
    21 posts
    Registered:
    12 Nov 2009
    21 Dec 2010
    Link to this post
    On one of our Sitefinity 3.5 sites, when we set the Require SSL option to "yes", the system throws a page not found error.  This site has a domain alias and this issue is only impacting one of the two domains.  Do I need to make additional configuration settings in either sitefinity or the web.config to handle SSL with domain alias?

    Thanks,

    -Jason
  2. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    25 Nov 2016
    22 Dec 2010
    Link to this post
    Hi Jason,

    Sitefintiy's requirements are

    1. Require SSL is set for the page you want to run under SSL
    2. SSL should be set through IIS over the website or the alias.

    Sitefinity checks if the page you are looking for require SSL and we switch the port from HTTP to HTTPS are vice versa.


    Best wishes,
    Ivan Dimitrov
    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? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  3. Jason
    Jason avatar
    21 posts
    Registered:
    12 Nov 2009
    22 Dec 2010
    Link to this post
    Thanks for the reply Ivan.  I've got both of those items correctly set.  The actual port switch does take place but instead of displaying the form, I get a 404 message.  One difference between the two domains (this site has a domain alias in place) is that the ssl cert for the one that's throwing errors is invalid.  Would this cause sitefinity to present a 404?
  4. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    25 Nov 2016
    27 Dec 2010
    Link to this post
    Hello Jason,

    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
    Both - this is the default value- redirects in both directions regarding the RequireSSL property.

    Most probably there is some redirect that breaks the behavior of the aliased domain name.

    Regards,
    Ivan Dimitrov
    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? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items
  5. Jason
    Jason avatar
    21 posts
    Registered:
    12 Nov 2009
    30 Dec 2010
    Link to this post
    Solved....the SecureBindings metabase property for the second domain name was not set.
Register for webinar
5 posts, 0 answered