cookie problem when on dedicated pool
Printed From: Web Wiz Forums
Category: General Discussion
Forum Name: ASP.NET Discussion
Forum Description: Discussion and chat on ASP.NET related topics.
URL: https://forums.webwiz.net/forum_posts.asp?TID=27789
Printed Date: 28 March 2026 at 4:56pm
Software Version: Web Wiz Forums 12.08 - https://www.webwizforums.com
Topic: cookie problem when on dedicated pool
Posted By: urko
Subject: cookie problem when on dedicated pool
Date Posted: 04 September 2009 at 10:48am
Hi,
I'm having some problems with cookies when i moved from shared to
dedicated pool. After some discussion with my host they have told me
that cookies will expire in few minutes if im on dedicated pool.
This is what i have in config file:
<forms loginUrl="Login.aspx" defaultUrl="Login.aspx" protection="All" cookieless="UseCookies"
path="/rc" timeout="43200" name="Mycookie" slidingExpiration="true" />
|
this is what my host replyed:
Host: I have just consulted with my supervisor. And he explained that this issue could be possible because shared pool updates frequently. And that is why cookie technology could feel some trouble.
me: ok...so how can i solve that this will work on dedicated pool?
Host: That is impossible to solve due to the shared kind of our hosting service. That is shared Pool and you can not change it properties. But you can switch your plan to the VPS and you will get your own application pools.
me: ok...so if i move to dedicated cookies will not work ??
host: They will but not for a long time.
So my question is, is there a workaround to stay logged in or not??
Anykind of help would be great.
|
Replies:
Posted By: WebWiz-Bruce
Date Posted: 04 September 2009 at 11:49am
I have never heard so much crap in my life.
We use dedicated application pools for all websites on our shared hosting packages, however we use shared application pools on our older accounts so have experience of both.
Dedicated and shared application pools will not drop session cookies in this way. The only time they would is if the application pool was recycling. Which it sounds like is happening.
What allot of shared web hosts who offer dedicated application pools will do is limit the memory for dedicated application pools to recycle when a set limit is reached. This with many hosts is 100MB.
Typically an ASP.NET application will use around 150MB within a few minutes and up to around 200MB to 400MB of virtual address space.
This is why with our hosting packages we give 200MB of memory plus 600MB of virtual addaress space for each website added to our systems. We find this enough for all websites without the application pools recycling.
Ask your web host how much memory your application pool is given and if it is to little then the only thing I can suggest is that you look at our own hosting packages:-
http://www.webwiz.net/webhosting/" rel="nofollow - http://www.webwiz.net/webhosting/
-------------
https://www.webwiz.net/web-wiz-forums/forum-hosting.htm" rel="nofollow - Web Wiz Forums Hosting
https://www.webwiz.net/web-hosting/windows-web-hosting.htm" rel="nofollow - ASP.NET Web Hosting
|
Posted By: urko
Date Posted: 04 September 2009 at 12:36pm
thanks for the reply Bruce. Will ask them how much memory is on application...If it's too little then for sure i will consider moving my site because now site loads way too long...
-------------
Urko
|
|