Open
Bug 598243
Opened 13 years ago
Updated 1 year ago
Content-encoding error when temp drive is full
Categories
(Core :: Networking: Cache, defect, P3)
Tracking
()
UNCONFIRMED
People
(Reporter: shimerwing, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-backlog])
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.2.10) Gecko/20100914 Firefox/3.6.10 ( .NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.2.10) Gecko/20100914 Firefox/3.6.10 ( .NET CLR 3.5.30729) When the drive containing the temp folder (usually c:\documents and settings\user\local settings\temp on Windows) becomes full, Firefox begins generating content-encoding errors on all visited web pages. The Page Info window (Tools > Page Info) reports that the content encoding (listed under Type on the General tab) is of type application/x-html. This only appears to happen when the available space is very low (I noted it at 1.5mb free), and once space is freed, the error quits occurring. Errors are to be expected when the cache is full, of course, but I believe remedying the problem would be simpler if Firefox would report a full-cache error rather than a content-encoding one. Reproducible: Always Steps to Reproduce: 1. Empty Firefox cache 2. Completely fill hard disk containing cache folder (<2mb free) 3. Access any web page (used Google.com) Actual Results: Received content encoding error Expected Results: Expected page to load normally
Updated•13 years ago
|
Component: General → Networking: Cache
Product: Firefox → Core
QA Contact: general → networking.cache
Updated•13 years ago
|
Blocks: http_cache
Updated•8 years ago
|
Whiteboard: [necko-backlog]
Comment 1•6 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P1
Comment 2•6 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: P1 → P3
Updated•1 year ago
|
Severity: minor → S4
You need to log in
before you can comment on or make changes to this bug.
Description
•