Opened 16 years ago

Closed 16 years ago

Last modified 15 years ago

#1233 closed defect (fixed)

cache parameters not working

Reported by: [email protected] Owned by: mumme
Priority: blocker Milestone:
Component: Widgets Version: 0.3
Keywords: Cc:
Blocked By: Blocking:


I'm using a DOJO Tooltip widget which gets its contents from a JSP. Everytime the user hovers over the image, a call should be made and the content should be updated accordingly.

Ever since I updated to the latest version of DOJO, it seems that using the cacheContent/refreshOnShow or the preventCache parameters in ContentPane? (the Tooltip superclass) don't work. IE seems to cache data anyway. Previously, using cacheContent worked fine.

Change History (5)

comment:1 Changed 16 years ago by mumme

Owner: changed from bill to mumme

Some clarifications just so we are on the same level: cacheContent=true results in a io.bind arg. useCache=true and preventCache=false And the opposite if cacheContent=false

the preventCache and useCache parameter to be able to do useCache=false to turn of javascript cache, saves memory preventCache=false dont append rubbish to the get string, ie use browsers cache

Only setting cacheContent should result in the same behaviour as before.

That said I'm thinking of delete useCache and preventCache in faviour of bindArgs That way a user could get nearer to the actual bind obj to do some other custom settings.

Bill: I can take this bug as I commited these parameters, if you want it back just claim it again

/ Fredrik

comment:2 Changed 16 years ago by dylan

Milestone: 0.4

comment:3 Changed 16 years ago by mumme

Resolution: fixed
Status: newclosed

Fixed in r5228,

the preventCache, useCache api is: ... bindArgs="preventCache:false;useCache:false;"

These settings override cacheContent so if you leave them out things should work as before.

comment:4 Changed 16 years ago by [email protected]

For everyone's information, the problem was NOT from the cache parameters in DOJO. I had to force prevent caching from the webapp itself using:

response.setHeader("Cache-Control","no-cache");	//HTTP 1.1
response.setHeader("Pragma","no-cache"); //HTTP 1.0
response.setDateHeader ("Expires", 0); //prevents caching at the proxy server


comment:5 Changed 15 years ago by (none)

Milestone: 0.4

Milestone 0.4 deleted

Note: See TracTickets for help on using tickets.