Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

"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.

Jan 10, 2008 11:40 AM in response to jaybrewer

I believe the vector for this problem, Jay, is that we recently introduced G-ZIP compression on our servers at Green Mountain. It looks like this issue has been around a while (between Safari and server compression) and we'll likely implement a quick fix by excluding Safari clients from compression, sending them uncompressed content, instead.

Jan 12, 2008 5:18 AM in response to deCadmus

That is what I noticed as well. As soon as I turned on gzip compression on one of my websites the result was the error mentioned above.

In my opinion this might have something todo with the way safari caches compressed websites, since it works if you access previously cached content that has changed in the meantime.

"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 ID.