Closed
Bug 846141
Opened 12 years ago
Closed 11 years ago
Content Encoding Error
Categories
(Core :: Networking, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: djmixon, Unassigned)
References
Details
Attachments
(1 file)
98.23 KB,
image/png
|
Details |
I am using Windows 7 64-bit.
I have been blocked from opening pages in Firefox both when following a valid link AND when typing in the address.
I can open the pages in IE9.
My husband can open the pages in both IE9 AND Firefox 19. Our configurations are identical.
We use cable internet with a wireless network.
Here is the error generated
Content Encoding Error
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.
Reproducible: Always
Steps to Reproduce:
1. Open Firefox
2. Type in www.mozilla.org
OR Type in http://input.mozilla.org/en-US/feedback#sad
OR Type in just about ANY OTHER WEBSITE
OR Follow just about ANY LINK FROM ANY OTHER WEBSITE
Actual Results:
Website does not open.
Expected Results:
Website SHOULD open.
This is happening with such regularity that I am ready to ditch Firefox and move on. It happens all the time, even after I empty my cache entirely via Tools>Options.
I am using the system proxy settings which allow me to get to the internet just fine using ANY OTHER BROWSER.
I tried to submit an error before, and although I got to this page, that bug report does not exist in your database.
Use this report. It contains more information.
Make a test with a fresh profile and your proxy settings: https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles
Anyway, it could be a proxy issue.
Updated•12 years ago
|
Flags: needinfo?(djmixon)
I don't use a proxy. I stated this up front.
This is an ongoing issue.
I have made a test with a fresh profile. NO PROXY because I am using cable broadband on a network which DOES NOT REQUIRE PROXY settings.
Again.
Firefox FAILS.
Any USEFUL advice?
Flags: needinfo?(djmixon)
Comment 5•12 years ago
|
||
This error code is generated when the compressed data Firefox receives from the web server is corrupt or otherwise fails to decompress successfully. I've not seen other reports of this problem, so I'd suspect the root problem is either something about your network or on your computer. Possibly malware. Run a scan?
You say you're not using a proxy. Have you confirmed that by checking Options --> Advanced --> Network, click the Settings button (in the Connection section), and ensure it's set to "No Proxy"? The default setting picks up settings from elsewhere on your system; explicitly setting this to "No Proxy" should skip that.
A debug build _might_ show some extra useful info... You can install a build from http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/2013-03-13-mozilla-central-debug/, run that firefox.exe with the -console flag, and watch for error messages in the extra terminal window.
Component: General → Networking
Product: Firefox → Core
Comment 6•12 years ago
|
||
Thanks for the bug report. We'll try to get to the bottom of this.
> I am using Windows 7 64-bit...
> My husband can open the pages in both IE9 AND Firefox 19. Our configurations
> are identical.
Just to be clear: you're using Windows 7 64 bit and Firefox 19? Is your husband using the same computer, or a different one (also Windows 7)?
Justin is right that this generally only happens if there's an error uncompressing compressed content (we can also hit it if a partial cache entry has mismatched content-encoding from the network channel; but that would be even more unlikely to happen for every single URI you visit). I also haven't seen anyone else with this issue... weird.
Comment 7•12 years ago
|
||
You can reproduce the content encoding error reliably from http://hendry.iki.fi on a fresh Firefox install (rm -rf ~/.mozilla)
Comment 9•11 years ago
|
||
Yes, tbh this bug has gone away for me. I think twitter have corrected something.
Flags: needinfo?(hendry)
Comment 10•11 years ago
|
||
Thx. Feel free to reopen if it's back.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
Comment 11•10 years ago
|
||
This bug is still around in FF 43.0.4.
User Agent: Mozilla/5.0 (Windows NT 6.1; rv:43.0) Gecko/20100101 Firefox/43.0
Build ID: 20160105164030
Version: 43.0.4
Steps that reproduced the bug:
Going to mail.yahoo.com and logging in to strictly a @yahoo.com email account(not happening with a @sbcglobal.net email account)generated this bug.
Comment 12•10 years ago
|
||
Open a new bug, this one is closed.
You need to log in
before you can comment on or make changes to this bug.
Description
•