I realise that I might be adding the odd unnecessary page to the
cache, but it's a small price to pay to get it working again, unless
anyone sees any problems with that approach?
The main problem is that you're covering up something that's broken in
your app that is likely to bite you eventually .... I would recommend
tracking down what is actually wrong. I have seen this happen before
if you have an image, CSS, or a file referenced from CSS, that is
using a relative path that is being interpreted as relative to a
component action, and blowing away/corrupting your session info on the
page. I would look at all your resource references for this page --
Easiest way is to look at the Activity Window in Safari and you will
see everything that is loaded and you should look for one that is
listed as missing or failed. It's not guaranteed to be this, but
there aren't very many things that break sessions like you're seeing.
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
