Re: bizarre session time-outs
Re: bizarre session time-outs
- Subject: Re: bizarre session time-outs
- From: Chuck Hill <email@hidden>
- Date: Thu, 3 Jun 2010 06:59:58 -0700
HI Simon,
On Jun 3, 2010, at 3:28 AM, Simon wrote:
hi all -
we've got a session time-out issue that is affecting just 1 specific
client. all other users of the app are happy - it's just not working
for this one company.
basically, as users form this one company click around the app they
randomly get instant session time-out's. no browser hanging -
instant back to login page. we are not seeing any instance failures
- the original instance the user was talking to is just sitting
there happily waiting for requests.
as the time out is instantaneous i thought maybe it's just that
monitor for some reason is randomly reporting that the instance they
are talking to is no longer there. but i'm suspicious of the fact
that only one specific client is affected.
i'm wondering if it's something to do the connectivity between the
client and the apps (yes, yes, i'm clutching at straws, i know!) but
can't think of any logical reason how or why it would affect things.
the only thing remotely strange about the client's set up is that
all the users internet traffic (users are in the UK) is routed
through their parent companies proxy in munich. is there any
possibility that the requests are somehow getting mangled by the
proxy ?
My first guess was "they are behind a proxy server" at the first line
in this message. See if you can get your domain excluded from the
proxy's caching or whatever else it is doing to the requests. Is the
server they are hitting unique to the client? OS X? Then make sure
that it is not running mod_proxy. I've also seen things like this
when mod_expires allows caching of WO content (I don't recall the
exact situation, something about requests made rapidly: automated
tests, or double clicking in the browser or Ajax or something like
that). You could try adding this to your httpd.conf:
ExpiresByType text/html A0
e.g.
<IfModule mod_expires.c>
ExpiresActive On
ExpiresDefault A60
ExpiresByType text/html A0
I found that this comment seem to be incorrect regarding the effect of
setting that header:
#### Make sure your CGIs return a "Cache-Control: no-cache" header if
you
#### elect to make your dynamically generated HTML pages not cache-able.
#### If all your HTML pages are static you may also increase
ExpiresDefault.
Chuck
any hints appreciated!
thanks, simon
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden