Ask a Question related to ASP.NET Security, Design and Development.
-
JimFoye #1
Can't persist the cookie
ticket is an instance of FormsAuthenticationTicket;
HttpCookie cookie = new HttpCookie(FormsAuthentication.FormsCookieName,
FormsAuthentication.Encrypt(ticket));
if (ticket.IsPersistent)
cookie.Expires = DateTime.Now.AddYears(1);
Response.Cookies.Add(cookie);
I added the 2 lines to set cookie expiration after seeing that in an article
written by an MS employee. Alas, it doesn't help.
Any ideas?
JimFoye Guest
-
HTTP::Cookie won't store sent cookie
Hi all, My script requests http://foo.bar.com/ with code that looks a little like this: my $ua = LWP::UserAgent->new; my $cookie_jar =... -
Manually created Cookie with UserData won't persist
I'm manually creating a FormsAuthenticationTicket and adding userdata. The problem is that the cookie won't persist. Code:... -
persist an array of data
I have a webservices that needs to keep internally an array of counters shared to every session and that should not be cleared even against machine... -
Cookies set one time, I delete cookie, cookie is never set again!
I am having this problem: My PHP script will set a cookie, it's there in my /Cookies folder. I delete the cookie (I have to for testing purposes,... -
authentication cookie vs session cookie
Hi, What are the differences between authentication and session cookies? In my web.config file, I set the cookieless attribute for the... -
v.m #2
Re: Can't persist the cookie
Did you try.
cookie.Expires = DateTime.Now.AddYears(-1);
HTH,
venkat.Murthy
"JimFoye" <JimFoye@discussions.microsoft.com> wrote in message
news:ED07E442-7148-41A8-9597-3EF531278EDE@microsoft.com...> ticket is an instance of FormsAuthenticationTicket;
>
> HttpCookie cookie = new HttpCookie(FormsAuthentication.FormsCookieName,
> FormsAuthentication.Encrypt(ticket));
>
> if (ticket.IsPersistent)
> cookie.Expires = DateTime.Now.AddYears(1);
>
> Response.Cookies.Add(cookie);
>
> I added the 2 lines to set cookie expiration after seeing that in an
> article
> written by an MS employee. Alas, it doesn't help.
>
> Any ideas?
>
v.m Guest
-
JimFoye #3
Re: Can't persist the cookie
That doesn't help. Why would setting the expiration back a year help? But I
appreciate the response.
The authentication API seems very confused. Why is a ticket persistent?
Isn't the cookie persistent? Would I want to persist the cookie and not the
ticket, or vice versa? And why do the published code samples NOT WORK?
"v.m" wrote:
> Did you try.
>
> cookie.Expires = DateTime.Now.AddYears(-1);
>
> HTH,
> venkat.Murthy
>
>
> "JimFoye" <JimFoye@discussions.microsoft.com> wrote in message
> news:ED07E442-7148-41A8-9597-3EF531278EDE@microsoft.com...>> > ticket is an instance of FormsAuthenticationTicket;
> >
> > HttpCookie cookie = new HttpCookie(FormsAuthentication.FormsCookieName,
> > FormsAuthentication.Encrypt(ticket));
> >
> > if (ticket.IsPersistent)
> > cookie.Expires = DateTime.Now.AddYears(1);
> >
> > Response.Cookies.Add(cookie);
> >
> > I added the 2 lines to set cookie expiration after seeing that in an
> > article
> > written by an MS employee. Alas, it doesn't help.
> >
> > Any ideas?
> >
>
>JimFoye Guest
-
Jim Foye #4
Re: Can't persist the cookie
Here's another example of API confusion. I can add a cookie, or I can set a
cookie. Hmmmm.....that's clear as mud, isn't it? What does it mean to call
set on a collection? But there it is
Context.Response.Cookies.Set(cookie);
I defy anyone to tell me that's logical.
"v.m" wrote:
> Did you try.
>
> cookie.Expires = DateTime.Now.AddYears(-1);
>
> HTH,
> venkat.Murthy
>
>
> "JimFoye" <JimFoye@discussions.microsoft.com> wrote in message
> news:ED07E442-7148-41A8-9597-3EF531278EDE@microsoft.com...>> > ticket is an instance of FormsAuthenticationTicket;
> >
> > HttpCookie cookie = new HttpCookie(FormsAuthentication.FormsCookieName,
> > FormsAuthentication.Encrypt(ticket));
> >
> > if (ticket.IsPersistent)
> > cookie.Expires = DateTime.Now.AddYears(1);
> >
> > Response.Cookies.Add(cookie);
> >
> > I added the 2 lines to set cookie expiration after seeing that in an
> > article
> > written by an MS employee. Alas, it doesn't help.
> >
> > Any ideas?
> >
>
>Jim Foye Guest



Reply With Quote

