This is the annoying IE bug. Even with the best cache breaking strategies
setup you won't be able to fix it unless you make the urls being used
unique. With dojo all you have to do is set preventCache:true in the
dojo.io.bind calls.
On 9/13/06, Vinicius Carvalho <[EMAIL PROTECTED]> wrote:
Sorry about the OT, but since we have some masters of Ajax/JS here,
I'm giving a shot.
Today we experienced problems with our chat application. When running
in clients that pass though a proxy, and use IE (this does not happens
to Mozzila browsers). The user receives only the same message, and
loops through it. What really happens is that the request never made
to the server, so the user get the same message over and over.
To try to bypass it. I've add the following to the function that polls
the server:
http_request.setRequestHeader("Cache-Control","no-store, no-cache,
must-revalidate");
http_request.setRequestHeader("Cache-Control","post-check=0,
pre-check=0");
http_request.setRequestHeader("Pragma", "no-cache");
But the errors keep happening.
Does anyone has any idea on how can I solve this?
Regards
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Jesse Kuhnert
Tapestry/Dojo/(and a dash of TestNG), team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
