3.0 beta 2

Caching ActiveWidget

Hi guys!

I was wondering if I could disable caching active widget in IE 6. It has been a failure by putting those meta tags and jsp tags. Nothing seems to stop it from caching. Enlighten me please.


December 20,
Does your case have an iframe? And are your asking it only for your development and testing environment? If so.. go to Tools->Inet Options...
General (tab)->Settings->Check for newer versions of stored pages->Every visit to the page

This should solve your problem
Md. Sheriff, Drivestream
December 20,
Thanks Sheriff,

It did help me in my development stage. I was wondering if there is a code that does the same thing in the production environment. In this case, I wasn't using any iframe at all. It is just a plain jsp.

The main objective is : active widget should not be cached in IE.

Thanks again,

December 20,
Md. Sheriff, Drivestream
December 20,
I had the same problem. it is due to requesting the same url to retrive your data from the server. The key is to make every request unique. You can do this by adding a timestamp to the url request.

when creating the table and loading it the first time.
var D = new Date();
  var url = "data.php?t=guest&m=" + D.getTime();

by adding the &m=" D.getTime()" to the url it makes every request unique.

Here is a function I created to deal with all the problems I encountered with loading the grid with new data when grid is refreshed.
// REload the Members table with updated data
function load(url){
  var Da = new Date();
  url += "&m=" + Da.getTime();	// Done to deal with page cacheing
  obj.clearRowModel();	// Clear Members Data Table to deal with polution
  table.setURL(url);		// Set the URL the Members table will read from
  table.request();		// Tell Table to request the data

hope this helps.
David Gutierrez
December 21,
I have exactly the same problem. I searched the internet so hard and could not find any direct answers. But only David Gutierrez's solution worked for me. Thanks a lot !

Jonathan @
Jonathan Lee
December 4,
We had a similar problem and implemented the same sort of technique. It's not that AW is caching the data - IE is caching the data. So by altering the URL and making it unique, it breaks the IE cache mechanism and loads the data file every time.

We have a timed event that needs the dataa to refresh. That's how we made it work. it was very frustrating until we figured out what was causing the data not to refresh.

It would be great if Alex altered his request code to automatically alter the url automatically (adding the parameter). Until then, David's solution works.
December 4,
It's minor, but using


instead of the date method saves a line of code.
David K
December 5,

The only possible problem with this thought it that it is not always guarenteed unique, that is

10 1 3 5 10 8 10

is a possible random sequence, hence the browser might invoke its cache for each instance when the random number was 10, whereas the time solution is always unique provided you don't do more than one request a second.
Mark H
December 20,

This topic is archived.

See also:

Back to support forum


Version 2

Looking for AW 2.6 ?
The old site is here.