Cookie Expiration is not more than 6 minutes at online Hosting

Question

1.00/5 (1 vote)

See more:

In login form, I set cookie expiration to 120 minutes. It's working in my local machine. But It's not working at Online Hosting Server. But when I set expiration to 15 seconds or 1 minutes, it's working at Online Hosting Server. If I set to long time, it's only work for 6 minutes. The cookie expiration is no longer than 6 minutes at Online Hosting Server. I use Plesk Web Host Edition. I change session timeout in ASP.NET Settings. But it's still not working. Where do I need to change setting. I did not found the solution in also Help Guide of Plesk.

I set cookie like this

FormsAuthenticationTicket authTicket = new FormsAuthenticationTicket(1, checkUser.UserName, DateTime.Now, DateTime.Now.AddMinutes(FormsAuthentication.Timeout.TotalMinutes), true, "");
string encTicket = FormsAuthentication.Encrypt(authTicket);
HttpCookie faCookie = new HttpCookie(FormsAuthentication.FormsCookieName, encTicket);
Response.Cookies.Add(faCookie);

In Web Config,

<authentication mode="Forms">
<forms name="mitf" loginUrl="~/Account/LogIn" timeout="120" />

<sessionstate timeout="120">

VB.NET

Can anyone help me please...

Posted 19-Dec-15 18:43pm

Member 10732171

Add a Solution

Comments

jgakenhe 20-Dec-15 1:15am

It sounds like they're restarting the app pool or web server a lot. If you restart either of those or make a change to the web.config, it will kill the session. You should create a ticket with the hosting company and see if it continues.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Accepted Answer · 2015-12-19T20:59:00

Cookie duration is a client based operation, so it's very, very unlikely that it's Cookies that cause the problem - it's possible that a "new" browser may ignore cookie expiration and deleted them early, but it's very unlikely, and doesn't happen with any on the main four.
So it's probably the Session, rather than Cookies.
You need to talk to your hosting company: some (particularly the cheaper end of the market) restrict the Session to a short interval than the standard 20 minutes, in order to maximise available resources. If they do, then generally it doesn't matter what value you try to set, anything longer than the new default will be ignored. They may be able to extend this for you - or move to a different hosting company which doesn't reduce the duration.