Wednesday, September 13th, 2006
David Arthur, like many, has had problems with the caching issue that Internet Explorer seems to have with Ajax connections:
If youâ€™ve been working with the Ajax framework long enough, iâ€™m sure youâ€™ve run into at least a few speed bumps thanks to Internet Explorer. Not a day goes by that i donâ€™t have to rewrite a line of code, or tweak my css in order for IE to render what i think it should. But alas, this is the nature of software that comes from a company that views Standard Compliances as recommendations.
He describes his problem – grabbing a new image with an Aajx request, a seemingly simple task – and the results of his queries. IE decided caching it was the “in” thing and wasn’t going to grab anything new. He tried all sorts of hacks and fixes to try to get things working, but to no avail. Finally, after finding this entry on Wikipedia, he stumbled across a solution – using POST over GET.
While he was figuring it out, though, there were also lots of comments being made to the original post with hacks to get around the issue – so many that he wanted to create a new place for them all to be shared. In this post he includes two of the suggestions, including using something like a timestamp to change up the URL and adding in an unused POST variable.
Posted by Chris Cornutt at 8:25 am