| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
This is to match the behaviour of the Android Java HTTP stack.
Bug: 3116410
Change-Id: I28fb1392c36754a7c2fd78bc76281db8318a1056
|
| |
|
|
|
|
|
|
|
|
| |
hasCookies(), removeExpiredCookie(), removeSessionCookie() and setCookie()
Requires a change to frameworks/base ...
https://android-git.corp.google.com/g/76898
Bug: 3116410
Change-Id: I6b881465f78e090ed29b215785c4018119ccc5d8
|
| |
|
|
|
|
| |
This matches the behaviour of the Android Java HTTP stack
Change-Id: I280e524a849dc93bae54795543b1440c3be98c27
|
| |
|
|
| |
Change-Id: I1b398bd0a84ce366eb2e686e5f14335d7aa5ed31
|
| |
|
|
|
|
|
|
| |
Requires a change to frameworks/base ...
https://android-git.corp.google.com/g/76605
Bug: 3116410
Change-Id: I1b66c1ac9f9aaf5388ad1da92f54b1f16d4a3626
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
HTTP stack
We also update PlatformBridge::cookiesEnabled() to query the Chromium
HTTP stack directly. This avoids calling
CookieClient::cookiesEnabled(), which calls the Java
CookieManager::acceptCookie() which in turns calls back to native
code.
Also requires a change to frameworks/base ...
https://android-git.corp.google.com/g/76065
Bug: 3116410
Change-Id: Id853463f3bcef76b220e8c44dd2b30c0d6752624
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
CookieSyncManager
Currently these paths are obtained from the BrowserFrame via JNI.
However, the paths are not synced to the BrowserFrame until the
WebCore thread has started up. This means that if the
WebRequestContext is created on the IO thread, the paths may not be
available.
This change moves the paths from BrowserFrame to CookieSyncManager to
avoid the need to wait for the WebCore thread.
Note that the new methods may be called on either the UI or WebCore
threads, so are synchronised.
Requires a change to frameworks/base ...
https://android-git.corp.google.com/g/76580
Change-Id: I61f88772d13901d66892118c79db3cac412e6bd1
|
| |
|
|
|
|
|
| |
This allows the method to be called from both the WebCore thread and
the UI thread, as required to hook up CookieManager.
Change-Id: I895d14909b14f0baba77fb2cb75926d9103ee01f
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously this file used Chromium style, as it extends a Chromium
class. However, I think it's best to switch to WebKit style to prevent
Chromium style from leaking into the rest of WebKit.
Also switches static member methods to file-scope static functions
where possible.
Finally, return WebRequestContext* rather than URLRequestContext* to
allow us to call methods in the derived class. this will be required
to hook up CookieManager.
Change-Id: Ifdca62230a3728e338904ef1b9b392640af06a92
|
| |
|
|
|
|
|
|
|
| |
This will be required when hooking up CookieManager to the Chromium
stack, as we need to decide in Java whether or not to call into native
code.
Bug: 3116410
Change-Id: I4e148ad2c38a6e5771912dc419f52c8098027958
|
| |
|
|
|
|
|
| |
Was broken by this CL:
https://android-git.corp.google.com/g/#change,75473
Change-Id: I6f60fd1e19eafe84f9d2f72f556493a25c2caf0e
|
|
|
Requires a change to frameworks/base ...
https://android-git.corp.google.com/g/75471
Bug: 3086308
Change-Id: I062015c990f6bc3d77ec22c746bd8465ed74bd08
|