Re: IE caching problem-
chris derham wrote: never had this problem when i deployed to SolarisI'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. That's not entirely accurate. It's more like browsers (and proxies) are allowed to cache response content for re-use, except when they are told otherwise. Roughly. The final truth is here : http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13 Have you used some kind of technique to check the headers? Fiddler or live http headers? Why are the pages being cached? That is the real question indeed. And indeed it may have something to do with the HTTP response headers (Expires, ETag, etc..) and/or with non-compliant browsers and proxies, and/or browser settings. So having a look at the HTTP headers would be a logical first step. 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 :-) This thread started reasonably enough, which will certainly have surprised some, considering the OP's historical record on this list. But I am afraid that it has now veered into matters of little relevance to Tomcat per se. In any case, I am fairly sure that Tomcat does not single out IE 9 among browsers, to sneakily introduce HTTP headers that would cause it to misbehave. Given IE's own historical record, I would rather think that the suspicion should be the other way around. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: IE caching problem-
On 14/05/2012 02:37, Martin Gainty wrote: i plan to run the windows IE code in Solaris thru WINE Eh?! How will that help? /rhetorical p thanks again, Martin From: mgai...@hotmail.com To: users@tomcat.apache.org Subject: RE: IE caching problem- Date: Sun, 13 May 2012 21:21:11 -0400 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 SolarisI'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 -- [key:62590808] signature.asc Description: OpenPGP digital signature
IE caching problem-
'Morning All I seem to be plagued by a IE caching problem where loading my index.jsp always returns the same old index.jsp my workarounds thus far: 1)Reload Webapp - TC still returns old index.jsp 2)Stop Webapp Start Webapp - TC still returns old index.jsp 3)delete webapps/WebAppName/index.jsp - TC still returns old index.jsp Environment: TC 6.0.20 IE: 9 Does anyone have suggestions to allow TC to return new index.jsp and not the old cached version? Thanks! 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.
Re: IE caching problem-
Did you delete the IE9 cache? Does the problem only exist on IE9? Ie, try chrome and firefox. Are the sizes of the old index.jsp different from the new index.jsp? Do you have any caching enabled/proxies etc? On 13/05/12 10:33 PM, Martin Gainty mgai...@hotmail.com wrote: 'Morning All I seem to be plagued by a IE caching problem where loading my index.jsp always returns the same old index.jsp my workarounds thus far: 1)Reload Webapp - TC still returns old index.jsp 2)Stop Webapp Start Webapp - TC still returns old index.jsp 3)delete webapps/WebAppName/index.jsp - TC still returns old index.jsp Environment: TC 6.0.20 IE: 9 Does anyone have suggestions to allow TC to return new index.jsp and not the old cached version? Thanks! 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. - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: IE caching problem-
2012/5/13 Martin Gainty mgai...@hotmail.com: 'Morning All I seem to be plagued by a IE caching problem where loading my index.jsp always returns the same old index.jsp my workarounds thus far: 1)Reload Webapp - TC still returns old index.jsp 2)Stop Webapp Start Webapp - TC still returns old index.jsp 3)delete webapps/WebAppName/index.jsp - TC still returns old index.jsp 4) pull out the network cable. If it does not help, then the problem is not in Tomcat. Anyway you have not tried to - Clear browser's cache - Undeploy and redeploy the webapp (or stop it and clear its work folder, - compiled JSPs are kept there) - Check whether clock time is correct on your PC and server Environment: TC 6.0.20 IE: 9 Does anyone have suggestions to allow TC to return new index.jsp and not the old cached version? Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: IE caching problem-
Date: Sun, 13 May 2012 18:13:02 +0400 Subject: Re: IE caching problem- From: knst.koli...@gmail.com To: users@tomcat.apache.org 2012/5/13 Martin Gainty mgai...@hotmail.com: 'Morning All I seem to be plagued by a IE caching problem where loading my index.jsp always returns the same old index.jsp my workarounds thus far: 1)Reload Webapp - TC still returns old index.jsp 2)Stop Webapp Start Webapp - TC still returns old index.jsp 3)delete webapps/WebAppName/index.jsp - TC still returns old index.jsp 4) pull out the network cable. MGwireless If it does not help, then the problem is not in Tomcat. Anyway you have not tried to - Clear browser's cache MGcleared Browseers cache - Undeploy and redeploy the webapp (or stop it and clear its work folder, - compiled JSPs are kept there) MGno jsp pages are currently stored or compiled into work - Check whether clock time is correct on your PC and server MGyep clock was incorrect Environment: TC 6.0.20 IE: 9 Does anyone have suggestions to allow TC to return new index.jsp and not the old cached version? Best regards, Konstantin Kolinko MGThanks Konstantin! MGMartin - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: IE caching problem-
On 13/05/2012 15:37, Martin Gainty wrote: Date: Sun, 13 May 2012 18:13:02 +0400 Subject: Re: IE caching problem- From: knst.koli...@gmail.com To: users@tomcat.apache.org 2012/5/13 Martin Gainty mgai...@hotmail.com: 'Morning All I seem to be plagued by a IE caching problem where loading my index.jsp always returns the same old index.jsp my workarounds thus far: 1)Reload Webapp - TC still returns old index.jsp 2)Stop Webapp Start Webapp - TC still returns old index.jsp 3)delete webapps/WebAppName/index.jsp - TC still returns old index.jsp 4) pull out the network cable. MGwireless If it does not help, then the problem is not in Tomcat. What about the power cable? p Anyway you have not tried to - Clear browser's cache MGcleared Browseers cache - Undeploy and redeploy the webapp (or stop it and clear its work folder, - compiled JSPs are kept there) MGno jsp pages are currently stored or compiled into work - Check whether clock time is correct on your PC and server MGyep clock was incorrect Environment: TC 6.0.20 IE: 9 Does anyone have suggestions to allow TC to return new index.jsp and not the old cached version? Best regards, Konstantin Kolinko MGThanks Konstantin! MGMartin - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org -- [key:62590808] signature.asc Description: OpenPGP digital signature
RE: IE caching problem-
never had this problem when i deployed to SolarisI'll try again tommorrow when i have a REAL Operating System to deploy my webapp Thanks Pid, 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. Date: Sun, 13 May 2012 18:21:16 +0100 From: p...@pidster.com To: users@tomcat.apache.org Subject: Re: IE caching problem- On 13/05/2012 15:37, Martin Gainty wrote: Date: Sun, 13 May 2012 18:13:02 +0400 Subject: Re: IE caching problem- From: knst.koli...@gmail.com To: users@tomcat.apache.org 2012/5/13 Martin Gainty mgai...@hotmail.com: 'Morning All I seem to be plagued by a IE caching problem where loading my index.jsp always returns the same old index.jsp my workarounds thus far: 1)Reload Webapp - TC still returns old index.jsp 2)Stop Webapp Start Webapp - TC still returns old index.jsp 3)delete webapps/WebAppName/index.jsp - TC still returns old index.jsp 4) pull out the network cable. MGwireless If it does not help, then the problem is not in Tomcat. What about the power cable? p Anyway you have not tried to - Clear browser's cache MGcleared Browseers cache - Undeploy and redeploy the webapp (or stop it and clear its work folder, - compiled JSPs are kept there) MGno jsp pages are currently stored or compiled into work - Check whether clock time is correct on your PC and server MGyep clock was incorrect Environment: TC 6.0.20 IE: 9 Does anyone have suggestions to allow TC to return new index.jsp and not the old cached version? Best regards, Konstantin Kolinko MGThanks Konstantin! MGMartin - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org -- [key:62590808]
Re: IE caching problem-
never had this problem when i deployed to SolarisI'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
RE: IE caching problem-
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 SolarisI'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
RE: IE caching problem-
i plan to run the windows IE code in Solaris thru WINE thanks again, Martin From: mgai...@hotmail.com To: users@tomcat.apache.org Subject: RE: IE caching problem- Date: Sun, 13 May 2012 21:21:11 -0400 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 SolarisI'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
Re: IE caching problem-
On Sun, May 13, 2012 at 6:21 PM, Martin Gainty mgai...@hotmail.com wrote: isolating the code from the browser is the logical first step Wouldn't it be easier to just use wget or curl or even telnet to fetch the page independently of *any* browser to see what's being sent? -- Hassan Schroeder hassan.schroe...@gmail.com http://about.me/hassanschroeder twitter: @hassan - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
