isolating the code from the browser is the logical first step
at least with solaris If i dont want pages cached then I can disable access
(with chmod and .htaccess) to the Temporary Internet Files folder and then when
IE tosses up error messages I can react appropriately
changing out browsers from IE to FF will further isolate and determine any
'tricks' that IE is playing ..without access to hidden folders and
unknown registry settings the IE caching problem can finally be determined
Many Thanks for your thoughtful response,
Martin--
______________________________________________
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger
sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung
oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem
Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung.
Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung
fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le
destinataire prévu, nous te demandons avec bonté que pour satisfaire informez
l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est
interdite. Ce message sert à l'information seulement et n'aura pas n'importe
quel effet légalement obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
> From: ch...@derham.me.uk
> Date: Sun, 13 May 2012 20:37:02 -0300
> Subject: Re: IE caching problem-
> To: users@tomcat.apache.org
>
> >
> > never had this problem when i deployed to Solaris....I'll try again
> > tommorrow when i have a REAL Operating System to deploy my webapp
> >
>
> So you have a web app, serving up web pages, that are being cached in a
> browser. The browser is not refreshing, for reasons unknown. You say that
> the clock was incorrect, but now I assume the problem is still occurring.
> Yet you think that moving the webapp to a "real os" will help?
>
> Browsers cache pages only if they are told to. Have you used some kind of
> technique to check the headers? Fiddler or live http headers? Why are the
> pages being cached?
>
> Once you know that, perhaps you can resolve the issue. If I had a car that
> wouldn't start, I know nothing about cars but I'm reasonably confident that
> changing the garage won't help the issue that much
>
> Chris
