Re: [ADVANCED-DOTNET] Strange cookie behavior

2005-01-14 Thread Muhammad Adel
Chad M. Gross wrote: If the user successfuly authenticate, a cookie should be put on his computer, which expires after 30 minutes.When I check the cookie expiration date from inside the browser, I find it is the expected time added to it 51 years! Sounds like you might be calling the FormsAuthenti

Re: [ADVANCED-DOTNET] Strange cookie behavior

2005-01-14 Thread Chad M. Gross
>If the user successfuly authenticate, a cookie should be put on his >computer, which expires after 30 minutes.When I check the cookie >expiration date from inside the browser, I find it is the expected time >added to it 51 years! Sounds like you might be calling the FormsAuthentication.SetAuthCoo

Re: [ADVANCED-DOTNET] Strange cookie behavior

2005-01-13 Thread Muhammad Adel
Brock Allen wrote: If the user successfuly authenticate, a cookie should be put on his computer, which expires after 30 minutes.When I check the cookie expiration date from inside the browser, I find it is the expected time added to it 51 years! For example if the cookie should expire on january 14

Re: [ADVANCED-DOTNET] Strange cookie behavior

2005-01-13 Thread Brock Allen
> If the user successfuly authenticate, a cookie should be put on his > computer, which expires after 30 minutes.When I check the cookie > expiration date from inside the browser, I find it is the > expected time > added to it 51 years! > For example if the cookie should expire on january 14 2004 a

[ADVANCED-DOTNET] Strange cookie behavior

2005-01-13 Thread Muhammad Adel
I am trying to use forms authentication in an application. I set the authentication element as follows in the web.config file: If the user successfuly authenticate, a cookie should be put on his computer, which expires after 30 minutes.When I check the cookie expiration dat