cookie values disappear when traversing between content pages

in my app. there’s a log in mechanism which save a cookie with the info of the user who just logged in

     private void CreateCookie(LoginEventArgs args)
     {
         HttpCookie cookie = new HttpCookie("user");
         cookie.Values["name"] = args.User_Name;
         cookie.Values["id"] = args.ID;
         cookie.Expires = DateTime.Now.AddDays(1);            
         Response.Cookies.Add(cookie);
     }

on my master page load i perform a check to see if this cookie exists or not :

   HttpCookie cookie = Request.Cookies["user"] ;
   if( (cookie != null) && (cookie.Value != ""))  
   {
        if (Session["user"] == null)
            Login_Passed(this, new LoginEventArgs(cookie.Values["name"].ToString(), int.Parse(cookie.Values["id"])));
   }

now if i Log in ( Create A cookie ) , close the browser , and run my app. again the cookie
exists it’s values are correct and the user is “automatically” logged in .

if i first redirect to a different content page from the start up content page
the cookies values are also intact ,

the problem is when i redirect back to a different content page a second time,
the master page loads , makes the check
the cookie exists but the values are deleted …

any ideas on why this happens ?

btw maybe the way i log out could be the reason for this problem :

when i log-out i create a cookie with the same name that expires 1 day ago .

   private void Remove_Cookie()
   {
        HttpCookie cookie = new HttpCookie("user");
        cookie.Expires = DateTime.Now.AddDays(-1);
        Response.Cookies.Add(cookie); 
   }

in the case iv’e described i don’t log-out formally , i just end my app , so this shouldn’t
have any effect .

Answers:

Thank you for visiting the Q&A section on Magenaut. Please note that all the answers may not help you solve the issue immediately. So please treat them as advisements. If you found the post helpful (or not), leave a comment & I’ll get back to you as soon as possible.

Method 1

o’k , the problem was unthinkable
special thanks to Peter Bromberg

http://www.eggheadcafe.com/tutorials/aspnet/198ce250-59da-4388-89e5-fce33d725aa7/aspnet-cookies-faq.aspx

in the section of the Article ” The Disappearing Cookie “

the author states that if you have a watch on Response.Cookies[“cookie_name”]
the browser creates a new empty cookie that overrides your cookie .

i used such a watch which made my cookie loose it’s values ,and when i took it off the cookie kept its values.

the moral is DON’t WATCH Response.Cookies[” “]
also i read in some other post that if you check

 if( Response.Cookies["cookie_name"] != null    )

for example it also gets overridden.

Method 2

To reiterate and build upon what has already been stated (yes, I know this is a 4 year old question) I have found it best to build a utility to handle this – mostly because I want to check that specific cookie often.

This will not touch the Response but only read from the Request.

    public static HttpCookie GetCookie(string cookieName)
    {
        HttpCookie rqstCookie = HttpContext.Current.Request.Cookies.Get(cookieName);
        /*** NOTE: it will not be on the Response!
         *   this will trigger the error noted in the original question and
         *   create a new, empty cookie which overrides it
         *   
            HttpCookie respCookie = HttpContext.Current.Response.Cookies.Get(cookieName);
         * 
         */
        if (rqstCookie != null && !String.IsNullOrEmpty(rqstCookie.Value))
        {
            // is found on the Request
            return rqstCookie;
        }
        else
        {
            return null;
        }
    }

rule-of-thumb

Always read from the Request and write to the Response.

Thanks eran! this post was exactly what I needed

Method 3

try the following:

• If you are developing on your local machine, put your app on some free web page, so there will be no ‘special treatment’ because you’re in the local host.
• If you already are on a web-server, and if the re-directions are between tow different domains, you may want to search google for ‘same origin policy’ or read this: http://en.wikipedia.org/wiki/Same_origin_policy (the document talks about javascript, but its true also for cookies).

Method 4

Use the following approach to get a value from cookies:

public string GetValueFromCookies(HttpCookieCollection cookies)
{
    if (cookies == null)
    {
        throw new ArgumentNullException(nameof(cookies));
    }

    // check the existence of key in the list first
    if (Array.IndexOf(cookies.AllKeys, key) < 0)
    {
        return null;
    }

    // because the following line adds a cookie with empty value if it's not there
    return cookies[key].Value;
}

All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0