Closed
Bug 1011873
Opened 11 years ago
Closed 11 years ago
Google Drive can not be used with new HTTP Cache
Categories
(Core :: Networking: Cache, defect)
Core
Networking: Cache
Tracking
()
RESOLVED
DUPLICATE
of bug 1010783
People
(Reporter: soeren.hentzschel, Assigned: mayhemer)
Details
With the new HTTP cache enabled (default since today) I cannot no longer use my Google Drive documents.
1. make sure that browser.cache.use_new_backend_temp is set to false
2. Go to your Google Drive overview and open a document
3. the document opens as expected
4. set browser.cache.use_new_backend_temp to true
5. repeat step 2
6. you will be redirected to https://support.google.com/accounts/answer/32050
7. restart your browser and test again
8. same problem as described in step 6
9. set browser.cache.use_new_backend_temp to false
10. repeat step 2
11. same problem as described in step 6
12. restart your browser and test again
13. repeat step 2
14. the document opens as expected
You can repeat the steps any number of times, the results is always the same. Google Drive is no longer usable with the new HTTP cache backend because Google redirects you to a help page about caching, a restart of the browser doesn't help. After disabling the new cache backend you have to restart the browser so that Google Drive works.
![]() |
Assignee | |
Comment 1•11 years ago
|
||
Simpler STR (100%):
1. Turn on the new cache, otherwise leave the preferences intact
2. Go to https://drive.google.com/?tab=wo&authuser=0#my-drive
3. Refresh (pure F5)
=> Page does NOT show the list, [ Loading... ] at the top is stuck
Broken content is served for few JS files (mainly https://drive.google.com/static/doclist/client/js/1101700167-doclist_modularized_core.js): SyntaxError: missing ; before statement 1101700167-doclist_modularized_core.js:1462
Note: served with Content-Encoding: gzip.
Workaround:
Set browser.cache.disk.preload_chunk_count to 0.
Regression from bug 1010221. Backing that change out helps, disabling it - by commenting out the continue; statement for loop - does NOT fix this bug.
Assignee: nobody → honzab.moz
Blocks: 1010221
Severity: normal → blocker
Status: UNCONFIRMED → NEW
Ever confirmed: true
![]() |
Assignee | |
Comment 2•11 years ago
|
||
Cause found, this is a problem with Read() implementation of cache input stream. Actually deps on 1010783.
![]() |
Assignee | |
Updated•11 years ago
|
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•