Comments on: Ajax Issue with Safari http://brennan.offwhite.net/blog/2005/03/21/ajax-issue-with-safari/ My Experiences with Software Development Tue, 07 Oct 2008 23:49:57 +0000 http://wordpress.org/?v=2.5.1 By: Joe http://brennan.offwhite.net/blog/2005/03/21/ajax-issue-with-safari/#comment-16969 Joe Thu, 29 Mar 2007 14:17:21 +0000 http://brennanwp.offwhite.net/blog/?p=116#comment-16969 now it's ok with RSS but still bug with Atom. now it's ok with RSS but still bug with Atom.

]]> By: Brian http://brennan.offwhite.net/blog/2005/03/21/ajax-issue-with-safari/#comment-133 Brian Fri, 24 Jun 2005 18:00:41 +0000 http://brennanwp.offwhite.net/blog/?p=116#comment-133 I have the same problem. I hacked around it by ensuring that my request was always unique. I just added the current time in milliseconds onto the end of my request, and it worked perfectly. I have the same problem. I hacked around it by ensuring that my request was always unique. I just added the current time in milliseconds onto the end of my request, and it worked perfectly.

]]> By: Jeremy Keith http://brennan.offwhite.net/blog/2005/03/21/ajax-issue-with-safari/#comment-132 Jeremy Keith Thu, 23 Jun 2005 12:10:14 +0000 http://brennanwp.offwhite.net/blog/?p=116#comment-132 I've been having a hell of a time with this same problem here: http://elsewhere.adactio.com/ It is indeed a caching issue. The only way to get around seems to be to *not* test for a status of 200. In effect, Safari is punishing you for being rigourous about status testing. If you assume that everything is okay, then Safari serves up the cached version. I guess you could still test for a status value of 200 or 'undefined'. Still... what a pain. I understand why caching is a good idea but it would be good to cache everything including the response status. I've been having a hell of a time with this same problem here:

http://elsewhere.adactio.com/

It is indeed a caching issue.

The only way to get around seems to be to *not* test for a status of 200.

In effect, Safari is punishing you for being rigourous about status testing. If you assume that everything is okay, then Safari serves up the cached version.

I guess you could still test for a status value of 200 or 'undefined'.

Still... what a pain. I understand why caching is a good idea but it would be good to cache everything including the response status.

]]> By: Brennan Stehling http://brennan.offwhite.net/blog/2005/03/21/ajax-issue-with-safari/#comment-131 Brennan Stehling Tue, 19 Apr 2005 14:41:33 +0000 http://brennanwp.offwhite.net/blog/?p=116#comment-131 I was actually working on testing that last night. That specific bug is fixed and that is great, but there now seems to be a new bug. I find that when I load a page which will generate more than one XHR request it will fail after the first one. But if I reload the page it can do as many requests as I like. With the RSS Include example you can load the page just fine but pressing the Load Headlines but will cause an error because the Request Status is undefined. I do not know why. Perhaps the content is cached and it simply knows that. Apple may be adding a feature which I need to learn about. I will post a new blog entry once I have the details worked out. I was actually working on testing that last night.

That specific bug is fixed and that is great, but there now seems to be a new bug. I find that when I load a page which will generate more than one XHR request it will fail after the first one. But if I reload the page it can do as many requests as I like. With the RSS Include example you can load the page just fine but pressing the Load Headlines but will cause an error because the Request Status is undefined. I do not know why. Perhaps the content is cached and it simply knows that. Apple may be adding a feature which I need to learn about.

I will post a new blog entry once I have the details worked out.

]]> By: Christopher Gervais http://brennan.offwhite.net/blog/2005/03/21/ajax-issue-with-safari/#comment-130 Christopher Gervais Tue, 19 Apr 2005 14:33:28 +0000 http://brennanwp.offwhite.net/blog/?p=116#comment-130 Is this fixed with Safari 1.3 (v312) included with the Mac OS X 10.3.9 update? Is this fixed with Safari 1.3 (v312) included with the Mac OS X 10.3.9 update?

]]>