Closed
Bug 2029199
Opened 6 months ago
Closed 5 months ago
Intermittent "Content Encoding Error" on google.com
Categories
(Core :: Networking: Cache, defect, P2)
Core
Networking: Cache
Tracking
()
RESOLVED
FIXED
151 Branch
| Tracking | Status | |
|---|---|---|
| firefox-esr140 | --- | unaffected |
| firefox149 | --- | unaffected |
| firefox150 | --- | unaffected |
| firefox151 | + | fixed |
People
(Reporter: mccr8, Assigned: jesup)
References
(Regression)
Details
(Keywords: regression, Whiteboard: [necko-triaged])
I started getting this error again intermittently.
Content Encoding Error
Nightly can’t connect to the server at www.google.com
What can you do about it?
The issue is most likely with the website, and there is nothing you can do to resolve it. You can notify the website’s administrator about the problem.
It looks like the pref was enabled again, but it is Nightly only.
Comment 1•6 months ago
|
||
Set release status flags based on info from the regressing bug 2013420
:jesup, since you are the author of the regressor, bug 2013420, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
status-firefox149:
--- → unaffected
status-firefox150:
--- → unaffected
status-firefox151:
--- → affected
status-firefox-esr140:
--- → unaffected
Flags: needinfo?(rjesup)
Updated•5 months ago
|
tracking-firefox151:
--- → +
| Assignee | ||
Comment 2•5 months ago
|
||
this is probably a dup of bug 2030119; we'll see once that hits central
Assignee: nobody → rjesup
Flags: needinfo?(rjesup)
| Reporter | ||
Comment 3•5 months ago
|
||
For what it is worth, I think I haven't experienced this for awhile.
Updated•5 months ago
|
Severity: -- → S3
Priority: -- → P2
Whiteboard: [necko-triaged]
| Assignee | ||
Updated•5 months ago
|
Updated•5 months ago
|
Updated•5 months ago
|
QA Whiteboard: [qa-triage-done-c152/b151]
You need to log in
before you can comment on or make changes to this bug.
Description
•