summaryrefslogtreecommitdiff
path: root/core/java/android/webkit/CacheManager.java
Commit message (Collapse)AuthorAgeFilesLines
* Use new UnsupportedAppUsage annotation.Artur Satayev2019-12-181-1/+1
| | | | | | | | Existing annotations in libcore/ and frameworks/ will deleted after the migration. This also means that any java library that compiles @UnsupportedAppUsage requires a direct dependency on "unsupportedappusage" java_library. Bug: 145132366 Test: m && diff unsupportedappusage_index.csv Change-Id: I5be7335b23a92b8ac80d2fd890198273b66ad644
* Add @UnsupportedAppUsage annotations for greylist.Artur Satayev2019-11-191-0/+5
| | | | | | | | | | | | | go/cleanup-greylist-txt These have already been greylisted, however due to bugs/omissions in the tooling have been kept in go/greylist-txt instead of being annotated in the code. This is partial merge of aosp/Id6c1f5e403a0e66edb1102ee45f3bf19f244fb09. Telephony greylist cleanup has been done separately. Note that annotations outside of frameworks/base/ have been merged from AOSP. Bug: 137350495 Test: m Exempt-From-Owner-Approval: merge Change-Id: I015c466e8b69cc0fed5e9d394ba865aad11d8ba6
* Add @UnsupportedAppUsage annotationsMathew Inwood2018-08-161-0/+38
| | | | | | | | | | | | | | | | For packages: android.webkit This is an automatically generated CL. See go/UnsupportedAppUsage for more details. Exempted-From-Owner-Approval: Mechanical changes to the codebase which have been approved by Android API council and announced on android-eng@ Bug: 110868826 Test: m Change-Id: I41643e1e47391a12b0aed3058b3d9987a8e6ee2f
* WebView: add @Nullable and @NonNull annotationsNate Fischer2017-09-211-1/+4
| | | | | | | | | | | | | | | | | This adds @Nullable and @NonNull annotations where the docs previously stated this. This change should be safe, since we already disallowed null values for the @NonNull parameters via documentation. I verified that documentation changes for APIs which previously did not mention null-ness in @param or @return Javadocs (if the API already mentioned it in these spots, then DroidDoc prefers the hand-written description). This also fixes various lint errors. Bug: 65465498 Test: make update-api and manually verify docs Change-Id: I4751508d0e72be8ddfc3d6b601db8c307c9df60e
* WebView: wrap Java literals with {@code}Nate Fischer2017-09-051-11/+11
| | | | | | | | | | | | | | | | Docs change only. This wraps some Java literals (true, false, null) with {@code} blocks, as per Android API guidelines. This also addresses other presubmit errors: * fix lines that have become too long * fix broken import order and unused imports Bug: 65213517 Test: make docs (and manually verify things look better) Change-Id: Idc7fe28d40bea7bd1edcad539b75fa9c689b8d46
* Remove unused imports from frameworks/base.John Spurlock2013-11-201-6/+0
| | | | Change-Id: Ia1f99bd2c1105b0b0f70aa614f1f4a67b2840906
* Restore 4 classes that were accidentally deletedJonathan Dixon2013-10-181-0/+341
| | | | | | | | | | Bug 11291911 These deleted classes were previously public APIs and so need to remain in the build (but hidden) in order to keep existing apps working. (Partially reverts Change-Id: I02549a71104b35d86d99058c71f43e054730ec7d) Change-Id: I28e53b056f41e66645136f5e18fba2ff55a65fe5
* Delete the old WebView.Torne (Richard Coles)2013-10-151-341/+0
| | | | | | | | | Delete all the Java classes used only by the old WebView implementation, and also sections of common classes that were only needed for the old WebView. Bug: 10427705 Change-Id: I02549a71104b35d86d99058c71f43e054730ec7d
* Remove CacheManager implementationBo Liu2012-10-241-122/+4
| | | | | | | CacheManager will not be implemented with webviewchromium. So removing existing implemntation in WebViewClassic. Change-Id: I82d3a156ba898393cc12080f8150841cd76f187a
* Hiding some of the deprecated android.webkit API'sKristian Monsen2012-09-071-0/+1
| | | | Change-Id: I1775a2ff615d1633fe9a20a5af49623222d3d27b
* Fix JavaDoc style for several WebView classesSteve Block2012-04-261-31/+55
| | | | | | | | | | | | | | | | | | | | | | | This fixes the JavaDoc style for the following classes ... - CacheManager.java - CookieManager.java - GeolocationPermissions.java - WebResourceResponse.java - WebSettings.java - WebStorage.java - WebView.java In particular, this applies the guidelines at https://wiki.corp.google.com/twiki/bin/view/Main/APIDocumentation This should help to ensure that future JavaDoc comments use correct style, rather than using incorrect style for consistency. Note that this change does not attempt to improve the content of the JavaDoc comments. This will be done in later changes. Bug: 5461416 Change-Id: I79e9b15a8cf3597195d58e154a7eb1bcc462944c
* Remove superfluous code after removal of Android HTTP stackSteve Block2012-03-261-8/+1
| | | | | | | See b/5495616. Bug: 6228353 Change-Id: I16cfd7b37973919d5bf14d2d80954caede264961
* Drop support for Android HTTP stackSteve Block2012-02-221-610/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | All future releases will use the Chromium HTTP stack and maintaining two HTTP stacks adds maintenance overhead. The Chromium HTTP stack requires V8, but we now use V8 in all build targets (b/5495373), so we can safely drop the Android HTTP stack. LoadListener, HttpAuthHandlerImpl, Network, SslErrorHandlerImpl, WebViewWorker - Android-stack specific, removed StreamLoader, FrameLoader - Require LoadListener, removed CacheLoader, ContentLoader, DataLoader, FileLoader - Extend StreamLoader, removed BrowserFrame - Removed methods that create LoadListener - BrowserFrame.startLoadingResource() is called from native CallbackProxy, WebView - Removed calls to Network methods CacheManager, CookieManager, CookieSyncManager, WebViewCore, WebResourceResponse - Removed other Android-stack specific code JniUtlil - Removed useChromiumHttpStack() WebViewDatabase - Removed all code to create cookies and cache databases for Android HTTP stack See corresponding WebKit change https://android-git.corp.google.com/g/166327. Bug: 5495616 Change-Id: If491675516f6eb187077af4220214bb6e6a8d045
* Remove unused cache methodsSteve Block2012-02-221-27/+1
| | | | | | | | | | | | | | | | | | | These were added in https://mondrian.corp.google.com/changelist/19077-p9. CacheManager.setCacheDisabled() has been unused since https://mondrian.corp.google.com/changelist/20678-p9 (see change to WebView), so the WebKit cache is always enabled. BrowserFrame.setCacheDisabled() has been unused since https://mondrian.corp.google.com/changelist/33679-p9, so the WebCore cache is always enabled. BrowserFrame.CacheDisabled() has been unused since https://mondrian.corp.google.com/changelist/32803-p9 (see change to WebView). See WebKit change https://android-git.corp.google.com/g/167298. Change-Id: I68bf334f4a34df1b88d2b5204e50c2eb04db7e69
* Clean up JavaDoc for CacheManagerSteve Block2012-02-211-62/+133
| | | | | | | Clean-up only, no functional change. Bug: 5461416 Change-Id: I272b1456e797f398014a6a4159319e5519fcaf64
* Fix CacheManager.getCacheFile() with the Chromium HTTP stackSteve Block2012-02-211-32/+48
| | | | | | | We need to populate the headers map with both the Android and Chromium HTTP stacks. Change-Id: I2df0aa2fce917ad43a1cac1426a324e49b2950f9
* am f7a9b869: am 1e7fb7ae: Merge "Error in compound cache-control header."Brad Fitzpatrick2011-03-301-1/+7
|\ | | | | | | | | * commit 'f7a9b8691918642db74a667a71028c0a77b527ff': Error in compound cache-control header.
| * Error in compound cache-control header.Henrik Baard2011-03-291-1/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | A cache control header containing both no-cache and max-age attribute does not behave as expected. Cache-Control: no-cache, max-age=200000 Will set expired to 20000ms seconds, ignoring the no-cache header. My interpretation is that the no-cache header should not be ignored in this case. Change-Id: Iadd1900e4d2c6c0dacc6bb3e7b944cf78ca9b266
| * Fix the last remaining @deprecated tag without comment warning.Joe Onorato2010-09-101-2/+2
| | | | | | | | Change-Id: Id4c50dee743fa781ca3f470f97ed76d1501f7222
* | Updated from comments to previous change after submittingKristian Monsen2011-02-161-4/+3
| | | | | | | | | | | | | | | | | | Previous change: https://android-git.corp.google.com/g/#change,91471 This change was to fix bug 3270236 Change-Id: I7dc3179a55420d3383647e2bd50d4766dd21231b
* | am f2b7c844: am 8d37c4ef: Merge "Tracking jarjar of org.bouncycastle to ↵Brian Carlstrom2011-01-251-2/+2
|\ \ | | | | | | | | | | | | | | | | | | com.android.org.bouncycastle" into honeycomb * commit 'f2b7c84468c5397b44566c393bec2675d73817b7': Tracking jarjar of org.bouncycastle to com.android.org.bouncycastle
| * | Tracking jarjar of org.bouncycastle to com.android.org.bouncycastleBrian Carlstrom2011-01-241-2/+2
| | | | | | | | | | | | | | | Bug: 3086427 Change-Id: I7af99fe4c36d9a519777f0499ccab65646313879
* | | am 6e8831cf: am 7450a32b: Merge "Clear the files we copy over to the temp ↵Kristian Monsen2011-01-201-2/+6
|\| | | | | | | | | | | | | | | | | | | | cache" into honeycomb * commit '6e8831cf2d7fd90ab124f58a9fc1919fac818887': Clear the files we copy over to the temp cache
| * | Clear the files we copy over to the temp cacheKristian Monsen2011-01-201-2/+6
| | | | | | | | | | | | | | | | | | Fixes CTS tests Change-Id: I3464ac90e58a9df21379a8da9d637f4f5ee69b85
* | | Documentation tweak for CacheManager.Iain Merrick2011-01-181-0/+2
|/ / | | | | | | | | | | It can't be used independently of WebView. Change-Id: Id90501ece0182481c7db541b5d1897782b7ee9c0
* | Hook up CacheManager for the Chromium HTTP stackSteve Block2011-01-141-8/+41
| | | | | | | | | | | | | | | | Requires a corresponding change in external/webkit https://android-git.corp.google.com/g/87938 Bug: 3270236 Change-Id: Ibb6ee0531bde48d9b069de28f9f22891ca6d0718
* | Avoid superfluous calls to CacheManager with the Chromium HTTP stackSteve Block2011-01-071-1/+50
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | Remove some superfluous null-checks when constructing a CacheResultSteve Block2011-01-061-11/+6
| | | | | | | | Change-Id: I57f0283872b788f84fef1667f79c37f4d92a5868
* | Tidy up CacheManager comments and documentationSteve Block2011-01-061-49/+53
| | | | | | | | Change-Id: I3a7d3836a51ef3092652ade87f29bc84af69ee7d
* | Remove an unused non-public CacheManager methodSteve Block2011-01-061-7/+0
| | | | | | | | Change-Id: Ia0bef0a66167ce948802701e1dd85e82b937dbdf
* | Deprecate CacheManager.Iain Merrick2010-12-171-3/+24
| | | | | | | | | | | | | | | | | | This class gives fairly low-level access to the HTTP cache, which as far as we can tell was only exposed for the benefit of Gears. BUG=3270236 Change-Id: Ibce10ecf8b524d3f472affa2a37fe4de15efd2ed
* | Add setContentLength method to CacheResult.Iain Merrick2010-12-171-0/+7
| | | | | | | | | | | | | | | | | | | | This is needed to construct a cachable CacheResult object. Currently only WebViewWorker is able to do this, by updating the fields directly. Bug: 3270236 Change-Id: I50148697dcee4d329e1436a2ce4c15224cb5ae30
* | *Don't* disable CacheManager when using Chromium HTTP stack.Iain Merrick2010-12-161-9/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | This reverts CL https://android-git.corp.google.com/g/84508 After lengthy discussion we have decided that disabling CacheManager is too risky for third-party apps, and that enough functionality is still available for it to be useful. WebView.loadUrl() will not add pages to the cache, but it is still possible to add them manually via CacheManager.saveCacheFile(). Change-Id: I6cfd9f93bb8d685450f048375adad9d17fa4eeba
* | Disable CacheManager when using the Chrome HTTP stack.Iain Merrick2010-12-131-0/+9
| | | | | | | | | | | | | | | | | | | | Currently, cacheDisabled() reports false, but no files are ever added to the cache. This CL makes the framework more honest and reports that the cache is disabled. BUG=3270236 Change-Id: I13c0291ac295d965f71f1e70dbdebc74b95ddce0
* | Fixes Android HTTP cache permissionsJohn Reck2010-12-101-1/+1
| | | | | | | | | | | | Bug: 3244281 Change-Id: I372475bc2d9bd2f2354ee603f77468df0cb043bf
* | Fix the last remaining @deprecated tag without comment warning.Joe Onorato2010-09-101-2/+2
| | | | | | | | Change-Id: I526707233652e8092b33357d08f8ed81cd3a9e14
* | Fix warnings in docs generation.Kristian Monsen2010-08-311-2/+2
|/ | | | | | This should fix the droiddoc warning related to the browser. Will make it a bit easier to pick up errors. Change-Id: I8dc276bbe3d15f224eba7e4e97046024173dcecc
* Move the public method HttpDateTime.parse() into AndroidHttpClient.Jesse Wilson2010-04-091-3/+3
| | | | | | See bug http://b/2553589 Change-Id: Ide3399c7c63daf9c0b8c18669076f2f4d6e9a876
* Fix for when flash loads cached crossdomain.xml files.Leon Clarke2010-03-231-0/+6
| | | | | Cache the x-permitted-cross-domain-policies header. http://b/issue?id=2519669
* As http header can't be empty, check length beforeGrace Kloba2010-03-191-2/+6
| | | | | setting lastModified and etag to the cacheResult. Fix http://b/issue?id=2531047
* Add a new WebCoreWorker thread to handle the tasksGrace Kloba2010-03-011-29/+63
| | | | | | | | | | | | | | | | | | | | | | | 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
* Re-arrange android-common so framework no longer links with it.Dianne Hackborn2010-02-251-1/+1
| | | | | | | This is the framework part, moving classes around so the framework no longer needs to link to android-common. Makes some APIs public, others that didn't need to be public are private in the framework, some small things are copied.
* remove android.webkit.HttpDateTime, againDoug Zongker2010-02-031-0/+2
| | | | | | | Remove this class, again, and change the webkit uses of it to use the one in android-common. Remove class from preloaded-classes as well. Change-Id: Ic0d4835e77180d299bc2c22b7c8780861b4781ee
* undo "move HttpDateTime from android.webkit to android-common jar"Doug Zongker2010-02-031-2/+0
| | | | | | | | | This restores this class to android.webkit, but leaves a copy in android-common while I figure out how to move it correctly. This reverts commit 7ad12a5f44253dc535f9a25ceb029579b40c43b1. Change-Id: I1d0a3efe34764058b979c6987e6e774f64d02b8c
* move HttpDateTime from android.webkit to android-common jarDoug Zongker2010-02-031-0/+2
| | | | | | Some to-be-unbundled classes want to use HttpDateTime as well. Change-Id: I40a001970682f6fbd4d9cd3546bd3f63ebfbe89b
* Make sure application cache manifest files are not cached.Andrei Popescu2010-02-021-0/+10
| | | | Fix b:2326937
* Cleanup the cache file when we decide not saving it.Grace Kloba2009-12-271-1/+15
| | | | | | | | | This logic was lost when we switched back using FLASH instead of RAM for the cache. Add back the CACHE_MAX_SIZE to limit the maximum cacheable file. Fix http://b/issue?id=2346132
* Fix a leak in WebView.Romain Guy2009-12-011-1/+1
| | | | | | | | Fixes #2296601. WebView and its related APIs are keeping static objects that hold references to Context instance. This could cause applications to leak their first Activity and all the associated resources.
* Update JavaDoc for CacheManger.CacheResult, ↵Ben Murdoch2009-11-191-0/+5
| | | | | | WebChromeClient.getDefaultVideoPoster and WebChromeClient.getVideoLoadingProgressView. Change-Id: I09e159cec0ccdf09b278daeeab268c0c4f4476ba
* Add postdata identifier so that if we cache the postGrace Kloba2009-11-081-8/+37
| | | | | | | result, we will use (url+postIdentifier) as the key for the CacheResult. Fix http://b/issue?id=1980031
generated by cgit v1.2.3 (git 2.25.1) at 2025-12-21 01:10:59 +0000