How do you guys deal with IE caching /base responses? Using the JQuery cache buster stuff fails cos it messes with the URL, currently I just have a spurious parameter (ieSucks) that has a random number in to get round the problem. Is there a better way to do this?
Passing a random numer in a querystring as you're already doing is a very comon approach. What jc is suggesting looks really interesting though and if it works it would be a more pretty solution.
@jc, I tried various permutations of that (I tried some of the other caching options too), with no luck, IE still cached it. I'm not sure if it's because the call is wrapped in the /Base methods or not, I need to debug it when I have more time!
For now I've stick with passing in a spurious timestamp to the methods so that they work ok, although I'm definately going to investigate this one further as it's a much neater way of doing it. Also, it amuses me to have a parameter called "fixIE".
Base and IE Caching
Hi,
How do you guys deal with IE caching /base responses? Using the JQuery cache buster stuff fails cos it messes with the URL, currently I just have a spurious parameter (ieSucks) that has a random number in to get round the problem. Is there a better way to do this?
Cheers,
Tim.
Can you try something like this in your /Base method?
Hi Tim
Passing a random numer in a querystring as you're already doing is a very comon approach. What jc is suggesting looks really interesting though and if it works it would be a more pretty solution.
/Jan
@jc, I tried various permutations of that (I tried some of the other caching options too), with no luck, IE still cached it. I'm not sure if it's because the call is wrapped in the /Base methods or not, I need to debug it when I have more time!
For now I've stick with passing in a spurious timestamp to the methods so that they work ok, although I'm definately going to investigate this one further as it's a much neater way of doing it. Also, it amuses me to have a parameter called "fixIE".
:P
is working on a reply...