tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Per Johnsson" <>
Subject RE: Tomcat cache problem?
Date Fri, 05 Jan 2007 13:19:03 GMT

I just want to enlight you about FireBug which is a FireFox plugin which
has a lot of stuff, including webserver communication:

It's a beta but its very promising and nice.

Another good way to se if a page is cached during debugging is a sysout
to the logfile, that way you really se if the jsp/servlet is executed.

/Per Jonsson

-----Original Message-----
From: Leon Rosenberg [] 
Sent: den 5 januari 2007 01:01
To: Tomcat Users List
Subject: Re: Tomcat cache problem?

the caching behaviour of the modern browsers is really a rocket science.
One of the way to try to control it is to put the according meta-tags
into your files:

		<META http-equiv="pragma" content="no-cache">
		<META http-equiv="Cache-Control" content="no-cache,
		<META name="Expires" content="0">

Furthermore I'd suggest you add a unique timestemp
(System.currentTimeMillis()) to each link (and change it on each page
reload). This way you can force the browser to believe he hasn't visited
the page yet.

That been said, you should really look into using a program which
displays browser-webserver communication. For firefox its
LiveHttpHeaders or TamperData , for IE a version of  LiveIEHttpHeaders
exists somewhere on the net.

When you see that your browser sends a valid new request and the servers
sends old data back you should start to check your webapp :-)


This e-mail and the information it contains may be privileged and/or
confidential.  It is for the intended addressee(s) only.
The unauthorised use, disclosure or copying of this e-mail, or any information it contains,
is prohibited. 
If you are not an intended recipient, please contact the sender and delete the material from
your computer.

To start a new topic, e-mail:
To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message