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

Forums / General Discussions / Question about TLD -> www.TLD redirecting

Question about TLD -> www.TLD redirecting

5 posts, 0 answered
  1. Keith
    Keith avatar
    67 posts
    Registered:
    13 Sep 2010
    29 Nov 2010
    Link to this post
    Hi,

    Our website is accessible by both example.com and www.example.com.  The problem we are having is when a user logs into the site via one, their session is not retained if switching to the other.  The two solutions that I can think of would be either redirecting example.com to www.example.com, or somehow getting the session to persist across both domains (www.example.com and example.com).

    So my question is, how would I go about accomplishing this in Sitefinity? Which of these two methods is better or is there a different and even better method?
  2. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    25 Nov 2016
    29 Nov 2010
    Link to this post
    Hello Keith,

    In Sitefinity we do not use a session, so you have some custom logic that works with session object. You can take a look at this discussion.

    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. Keith
    Keith avatar
    67 posts
    Registered:
    13 Sep 2010
    29 Nov 2010
    Link to this post
    I added:
    <httpCookies domain=".mydomain.com" />
    to my web.config as indicated in the link that you posted, however I am still having the same problem...
  4. Keith
    Keith avatar
    67 posts
    Registered:
    13 Sep 2010
    02 Dec 2010
    Link to this post
    Anyone?
  5. Ivan Dimitrov
    Ivan Dimitrov avatar
    16072 posts
    Registered:
    25 Nov 2016
    02 Dec 2010
    Link to this post
    Hi Keith,

    We do not use session. Most probably the problem is in the way that you are trying to authenticate your users. As you can see this is a standard ASP.NET configuration that allows you to authenticate yourself on both the instances. As another option you could try implementing Single Sign On.

    All the best,
    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
Register for webinar
5 posts, 0 answered