"Cannot decode raw data" error on safari

Hi,

I've been using Safari 3 that came installed with Leopard. Whenever I try to load a page from Flickr, I receive an error:

Safari can’t open the page.
Safari can’t open the page “ http://www.flickr.com/photos/...”. The error was: “cannot decode raw data” (NSURLErrorDomain:-1015) Please choose Report Bugs to Apple from the Safari menu, note the error number, and describe what you did before you saw this message.

I've done a search on this on the error on these forums and with google and haven't turned up anything. Does anyone have any ideas on what it could be?

Thank you very much for your help!

Stephen

Macbook Pro, Mac OS X (10.5)

Posted on Nov 8, 2007 1:43 AM

Reply
40 replies

Nov 21, 2007 1:36 PM in response to sbuzdug

One thing I've noticed, from experimenting, is that if I turn cookies off on Safari, I do not receive this error and all Flickr pages load successfully. When I turn cookies back on, the issue recurs.

Is there a problem with the way Safari handles cookies? If so, I wonder why I'm receiving this error and why I haven't seen this problem reported elsewhere.

Any thoughts, ideas or suggestions would be greatly appreciated!

Thank you!

Stephen

Dec 11, 2007 4:46 PM in response to mettzen

Not sure how helpful this will be to anyone who is having this problem on the 'End User Side', but for server admins and developers this may help narrow down the issue:

We were having this bug intermittently with our rss feeds on gluenow.com. An example of a feed is here: http://sqd.gluenow.com/news/rss. I didn't find much online about this bug, aside from here... so I ended up just systematically removing different headers from our application and tweaking apache settings. Through this I did manage to fix this bug, but I am not sure why it fixes it.

Some background, Glue uses an apache front-end proxy with multiple mongrel clusters running the back-end Ruby on Rails app. Before, when the error would occur, our server was emmiting a Via: header, indicating that the content was proxied via gluenow.com. Here is what the headers looked like (with irrelevant headers removed):

rails-1 vhosts.d # curl -I http://sqd.gluenow.com/news/rss
...
Via: 1.1 www.gluenow.com
Vary: Accept-Encoding

It seems that the "Via: 1.1 www.gluenow.com" header was causing the problem. I disabled the Via header in apache ( ProxyVia Off ), and now it works 100% of the time with no error.

So, at any rate, there are some examples in this thread that have the same issue, I would be interested if this workaround would fix them as well, or if they are even using the Via header right now (have not checked yet).

Hope this helps narrow down the cause of this issue.

Feb 1, 2008 3:14 AM in response to sbuzdug

This is a really issue that does not happen on other browsers. I get this problem a lot with Safari, but it never happens with FireFox or Opera. I think it has something to do with gzip compression, but I am not an expert.

This bug has been around for quite a long time, but Apple hasn't fixed it yet. I am really thinking about ditching Safari because of this. As some already mentioned earlier, it is becoming very annoying.

Feb 4, 2008 5:24 PM in response to sbuzdug

I've been having this problem intermittently since the days of Tiger. I'm glad to see it isn't just me. I was hoping it would be fixed in Leopard but it wasn't in the initial release. It occurs on all my Macs including my wife's Intel iMac and my Intel Macbook, as well as my G5 iMac. I've found that resetting Safari except for cookies and then quitting and restarting Safari will generally correct the problem, especially with eBay. However occasionally my Yahoo and eBay page displays get totally hosed. Logging out and logging back in doesn't help in those cases so I have to restart the computer, which is aggravating.

I try to report the error to Apple every time this error occurs - just like the error message says to. Seeing how many others have experienced it, they must be aware of it!

Mar 24, 2008 4:19 PM in response to sbuzdug

i get this error every time trying to use Google Checkout to send a invoice via email. I sent the bug report to Apple.


Possible part Solution:

weird thing that kinda works for me is. if i click on the link to load the page and it doesn't load, if i choose Disable Caches from the Develop menu, then reload the page works. when it doesn't work again, i just do the same thing.. This has it working somewhat, but still needs to be corrected

Apr 7, 2008 9:58 AM in response to sbuzdug

Of all the things I 'browse' it appears to happen the most often when visiting eBay sites. Still, it's something that should not happen, nor should I have to dump this cache, or change that setting to get it to work correctly 'a little more often.'

While it may be related to some server-side web server setting, it is maddening, especially while trying to run a web-based business. Having that error message come up when trying to post a payment is frustrating to the core.

Apr 17, 2008 6:00 PM in response to macfan55_nl

I can confirm that for ebay.com as well. It seems to show up randomly but mostly in the "My eBay" section. It is really annoying.
This problem has been reported since the launch of Leopard. Apple so far has not addressed this issue. Dealing with this browsing annoyance on a daily basis is truly a bad user experience. I am tired of waiting for a fix and getting bashed with error pages where no other browser chokes.
I switched to Mozilla Firefox for now. What a breeze not to have to deal with this annoying Safari behavior anymore.

May 7, 2008 9:03 PM in response to sbuzdug

I've been getting that error message on eBay for a long time now. I find it occurs mostly during peak usage hours...in the evening or right after dinner. I emailed my account executive at eBay a few weeks ago about the problem and he told me that the tech department was unaware of any problem with Safari. My fix is to keep Firefox open on my desktop....Now if I can only get around to moving all my Bookmarks over to Firefox I'd be OK. I hope Apple figures it out.....Ben

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

"Cannot decode raw data" error on safari

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.