On 3/26/2014 11:20 AM, »Q« wrote: > In <news:[email protected]>, > "Paul B. Gallagher" <[email protected]> wrote: > >> When trying to view stories at nydailynews.com, I often get this >> error message: >> >> Content Encoding Error >> >> The page you are trying to view cannot be shown because it uses an >> invalid or unsupported form of compression. >> >> The page you are trying to view cannot be shown because it uses an >> invalid or unsupported form of compression. >> >> Please contact the website owners to inform them of this problem. >> >> [Try again] >> >> [end quote] >> >> What's up with that? IE never has any problem displaying the pages, >> but SM won't even show me the source code. >> >> Here's an example, but pretty much any story from the "Editor's >> Picks" rubric on the right side of their pages does this: >> >> <http://www.nydailynews.com/opinion/drug-testing-welfare-recipients-big-mistake-conservatives-article-1.1734098> > > gzip compression is what's being used, but that's been standard on the > web for many years, and SM supports it fine. > > My only guess is that what you're getting is being mangled by a > transparent proxy between you and the server. Using shift+reload > *might* get around it. > > >
You might also try viewing the Web page in Safe Mode. I don't see any problem with AdBlock Plus, Flashblock, or Secret Agent; but some other extension in your configuration might be causing problems. -- David E. Ross <http://www.rossde.com/> On occasion, I filter and ignore all newsgroup messages posted through GoogleGroups via Google's G2/1.0 user agent because of spam, flames, and trolling from that source. _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
