P
Pete
Hi,
I didn't get any responses from the first post I made about this so I've
done a bit more investigation but I'm still having problems (but only in
Production (Win 2003) not development (XP Pro)). This leads me to think it's
a server config issue rather than code problem. Anyway here's the
problem....hope you can help.
My logged on users are randomly kicked out of my secure pages well before
the auth cookie expires. The persist cookie is working as I can see it
stored in the browser cache. Apparently their Forms Authenicated session has
expired however & there seems to be no pattern as to when it expires.
The standard user "Session" appears to be fine and lasts for the configured
length in Web.Config.
Here's what I've tried....
Changing the Forms Cookie name & Timeout.
Checking all code (it works exactly as expected on my XP Pro box)
Asked hosting provider if they broke it (said they didn't)
Is it possible that a setting in Machine.Config could be causing me these
issues? If so what section would it be?
Any ideas at all would be appreciated as I'm really stuck with this and my
users are not so happy.
thanks for looking
Pete
I didn't get any responses from the first post I made about this so I've
done a bit more investigation but I'm still having problems (but only in
Production (Win 2003) not development (XP Pro)). This leads me to think it's
a server config issue rather than code problem. Anyway here's the
problem....hope you can help.
My logged on users are randomly kicked out of my secure pages well before
the auth cookie expires. The persist cookie is working as I can see it
stored in the browser cache. Apparently their Forms Authenicated session has
expired however & there seems to be no pattern as to when it expires.
The standard user "Session" appears to be fine and lasts for the configured
length in Web.Config.
Here's what I've tried....
Changing the Forms Cookie name & Timeout.
Checking all code (it works exactly as expected on my XP Pro box)
Asked hosting provider if they broke it (said they didn't)
Is it possible that a setting in Machine.Config could be causing me these
issues? If so what section would it be?
Any ideas at all would be appreciated as I'm really stuck with this and my
users are not so happy.
thanks for looking
Pete