Home/ Questions/Q 9119115
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-17T05:19:03+00:00

I am having trouble with the .Expires cookie attribute. It keeps coming back with

  • 0

I am having trouble with the .Expires cookie attribute. It keeps coming back with 01/01/0001 12:00 AM, when I read the cookie back.

Here is the code. I added in the retrieve just below the save solely for debugging purposes. The save and retrieve happen in different places in the same file. I purposely did not specify a Domain, as I want the cookie to exist site wide.

The data shows up nicely, just not the expiration.

Note: I am testing under Visual Studio 2012 running under local host using .Net Framework 4.

System.Web.UI.Page oPage = this.Page;

HttpCookie oCookie = new HttpCookie("UserData");

// Set the cookie value.
oCookie.Secure = false;
oCookie["Field1"] = strField1;
oCookie["Field2"] = strField2;
oCookie.Expires = DateTime.Now.AddDays(1);

// Add the cookie.
oPage.Response.Cookies.Add(oCookie);


// Get the cookie.
oCookie = new HttpCookie("UserData");
oCookie = oPage.Request.Cookies["UserData"];
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The browser will not send anything to the server except the cookie name and value. All of the other properties (expires, domain, path, httponly, …) cannot be retrieved on requests after the cookie has been set.

    The more accepted way to deal with this is to redirect the user to a login page when they try to access a protected resource and display some message along the lines of “You need to log in to view this page. If you were previously logged in, your session may have expired.”

    (Also note that you should be re-setting the cookie on every request, so that the user will not be logged out if they continue to use the site. It’s not clear from your code whether you are doing this or not.)

    • 0