| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
Bug:3337213
Change-Id: Ic687bc506faba23c3e52e44f0a5d0146a352206e
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
When using the Chromium HTTP stack, most of the calls to CacheManager
methods are not required, as we're not using its cache. These methods
are now marked with asserts to make this clear.
Also avoid creating the cache database in WebViewDatabase.
This will avoid creating the database databases/webviewCache.db and
the directory cache/webviewCache.
Bug: 3270236
Change-Id: I68f94dde16830ed817454d5e1af961f41b71d018
|
| |
|
|
|
|
|
|
|
|
|
| |
This updates the strorage locations to better match those used by the
Android HTTP stack.
The corresponding external/webkit change is
https://android-git.corp.google.com/g/70643
Bug: 3039536
Change-Id: Ia7ea68d1472e96788a7fbaa6e8f7aa1ee51b3fb0
|
| |\
| |
| |
| |
| |
| |
| | |
Merge commit 'dc1f08586eadc3a3dbbdf22b520ba1065b2032f8'
* commit 'dc1f08586eadc3a3dbbdf22b520ba1065b2032f8':
Fix npe in getCacheTotalSize.
|
| | |
| |
| |
| |
| | |
Bug: 2882277
Change-Id: I9319a48e0ed75561d3d04691fb288f69d11edc84
|
| |/
|
|
|
|
|
|
|
|
|
|
|
| |
This isn't the perfect solution as any calls into WebViewDatabase will block
until initialization completes. It is better than the current model which
blocks when creating the WebViewDatabase.
In order to get a perfect solution, we would need to do initialization in the
background and have a way to interact with the database during initialization
that would not block.
Bug: 2721802
Change-Id: Ibbaf7f97926128de6534fbf2148452099766c6b7
|
| |
|
|
|
| |
Cache the x-permitted-cross-domain-policies header.
http://b/issue?id=2519669
|
| |
|
|
|
|
| |
Fix for http://b/issue?id=2533750
Change-Id: I3ebcc6147e4035ce1c4bf6b76a359ce14196e357
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
which should not block either UI or WebKit. It handles
local file access, cache access and trim cache.
Move createCache, saveCache and most of getCache out
of WebCore thread so that slow IO and database will
not affect loading performance. getCache can be still
called from WebCore thread in the uncommon cases
like redirect and POST validation.
Move cache ticker from WebCore thread to WebViewWorkerThread.
Move setCookie from WebCore thread to WebViewWorkerThread.
Remove the unreferenced files in the cache directory
while trim cache.
Confirmed with our SQL expert, Vasu, there is no need
to wrap clearCache with end/startTransaction any more.
http://b/issue?id=2414792
http://b/issue?id=2475242
|
| |
|
|
|
|
|
| |
the old db and re-do it. If it still fails, something
bad happens, like the directory may have the different
permission. Let it throw as WebView needs the db.
Fix http://b/issue?id=2179339
|
| |
|
| |
httpauth table.
|
| |
|
|
| |
As WebKit is using string version of "expires", pass it with the rest of the headers.
|
| |
|
|
| |
We have to upadte our cache database. Good thing is Gears can avoid the expensive date conversion.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
