Closed Bug 460818 Opened 16 years ago Closed 14 years ago

Content encoding error when trying to render www.bloomberg.com home page

Categories

(Firefox :: General, defect)

x86
Windows Vista
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: jim, Unassigned)

References

()

Details

(Whiteboard: [CLOSEME 2010-12-01])

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.3) Gecko/2008092417 Firefox/3.0.3

I frequently, but not always, receive a content encoding error when the browser is trying to render www.bloomberg.com home page. I also get the encoding error when trying to view source.

I never get this error when using either Chrome or IE7 on www.bloomberg.com.

Reproducible: Sometimes

Steps to Reproduce:
1. go to www.bloomberg.com
2.
3.
Actual Results:  
content encoding error

Expected Results:  
renders the home page
Here is the detailed error message:

"The page you are trying to view cannot be shown because it uses an invalid or unsupported form of compression."
I am using the adblock plus add-on
Problem exists with Windows XP Pro system as well
I'm running Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4 and can also confirm this error.  A Google search will show plenty of other Firefox users who run into this with www.bloomberg.com as well.

The error is:  "Content Encoding Error
The page you are trying to view cannot be shown because it uses an invalid or unsupported form of compression."

It only happens once you've already visited Bloomberg before, though I can't find any pattern that causes it to start happening (sometimes visiting Bloomberg and the revisiting it causes no problems, but a few days later it'll start showing the Content Encoding Error).

The only way to resolve it is to clear the cache, e.g. via Tools -> Options... -> Advanced -> Network -> Offline Storage -> Clear Now, which immediately fixes the problem.  As soon as the cache is cleared, visiting www.bloomberg.com works perfectly again, so there must be something in relation to cached data causing the problems.  It is worth noting that once it starts showing the Content Encoding Error, closing Firefox and launching it in Safe Mode also exhibits the same behaviour (until the cache is cleared, then it no longer gives the Content Encoding Error... at least for a while).
I run into this with www.bloomberg.com as well.

I am running Firefox 3.5.8 with OS/2.

Mozilla/5.0 (OS/2; U; Warp 4.5; de; rv:1.9.1.8) Gecko/20100218 Firefox/3.5.8

Kind regards

Rainer
Feedback from Bloomberg.com:

Feedback Status: TicketID: W00380532840574090170
Status: Resolved
Summary: To the Webmaster: Bug 460818 - Content encoding error when
LOG: 2/25/10 13:29:30 Your Initial Feedback
please have a look at the mozilla bug
https://bugzilla.mozilla.org/show_bug.cgi?id=460818 A google seachs shows many
people run into this "bug" kind regards Rainer
LOG: 3/31/10 14:09:05 Bloomberg Feedback Team
Hello; We were advised that all has been resolved on this end. Hopefully all is
OKAY on your end.
Sincerely, Bloomberg Website Feedback Team 


Does anybody still run into the problem?

Rainer
I haven't seen this in many months of using Firefox as my main browser under OS X.
Reporter, please retest with Firefox 3.6.12 or later in a fresh profile (http://support.mozilla.com/kb/Managing+profiles). Also update your plugins (flash, adobe reader, java, quicktime, silverlight, etc.) Go to the developer's website and download the latest version from there. If you no longer see this issue, please close this bug as RESOLVED, WORKSFORME. If you do see the bug, please post a comment.
Whiteboard: [CLOSEME 2010-12-01]
petergair added the following comment to Launchpad bug #375784:

Thanks, Tyler
I no longer see the bug.
The updates have fixed it.

Peter


On Sun, Nov 14, 2010 at 8:03 AM, Tyler Downer <tyler.downer@gmail.com>wrote:

> Reporter, please retest with Firefox 3.6.12 or later in a fresh profile
> (http://support.mozilla.com/kb/Managing+profiles). Also update your
> plugins (flash, adobe reader, java, quicktime, silverlight, etc.) Go to
> the developer's website and download the latest version from there. If
> you no longer see this issue, please close this bug as RESOLVED,
> WORKSFORME. If you do see the bug, please post a comment.
>
> --
> http://www.bloomberg.com will not load -- Content Encoding Error
> https://bugs.launchpad.net/bugs/375784
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in The Mozilla Firefox Browser: New
> Status in “firefox-3.0” package in Ubuntu: Triaged
>
> Bug description:
> Binary package hint: firefox-3.0
>
> This problem has been occurring for months.  On my Windows XP system, there
> are times when Firefox will not load www.bloomberg.com.  There, I can
> switch to Internet Explorer, which always loads the page.
> Endeavoring to move from Windows to Ubuntu, but now I have the same issue
> on Ubuntu.
> I suspect the issue has to do with an introductory Advertisement that is on
> bloomberg some times - usually a video.
> For me, access to bloomberg is essential.
> .
>
> ProblemType: Bug
> Architecture: i386
> DistroRelease: Ubuntu 9.04
> Package: firefox-3.0 3.0.10+nobinonly-0ubuntu0.9.04.1
> ProcEnviron:
>  PATH=(custom, no user)
>  LANG=en_AU.UTF-8
>  SHELL=/bin/bash
> SourcePackage: firefox-3.0
> Uname: Linux 2.6.28-11-generic i686
>
> WORKAROUND:
> <Thanks to Zyan (Upstream)>
> The only way to resolve it is to clear the cache, e.g. via Tools ->
> Options...
> -> Advanced -> Network -> Offline Storage -> Clear Now, which immediately
> fixes
> the problem.  As soon as the cache is cleared, visiting www.bloomberg.comworks
> perfectly again, so there must be something in relation to cached data
> causing
> the problems.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/firefox/+bug/375784/+subscribe
>


-- 
http://launchpad.net/bugs/375784
No reply, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.