83d4a23c280bdcaf6c301651b76ddc6fbf08949c |
|
12-Nov-2010 |
Iain Merrick <husky@google.com> |
Provide default error strings in BrowserFrame.onReceivedError(). This method is called from both the Android and Chrome HTTP stacks. We want the same user-facing behaviour in each case, but the Chrome code does not have easy access to the same error message strings. Therefore, I'll have the Chrome HTTP stack provide empty strings for the descriptions. (See change I9042a2ee in external/webkit). This CL makes BrowserFrame check for empty or null strings and use the standard error messages instead. The strings were package-private, so I did a little cleaning up to make them public (but still hidden from the API). Using a switch statement instead of an array because it's more robust and should be comparably efficient. Bug: 3172265 Test: Load http://google.com:81 to force a timeout error, check that the correct message is displayed. Change-Id: I7dec8dffe8ad9e513fdb90877e0b466e707174a8
/frameworks/base/core/java/android/net/http/EventHandler.java
|
dba8cb76371960457e91b31fa396478f809a5a34 |
|
19-Mar-2010 |
Brian Carlstrom <bdc@google.com> |
b/2511635 Browser displays incorrect SSL cert information Two more cases of "View certificate" problems like b/2511635 One problem is that if there are multiple resources downloaded for a page. In that case the mCertificate shown ends up being from the last loaded resource instead of the main resource of the page. The solution is to only set the certificate if the LoadListener is the mIsMainResourceLoader as well as the mIsMainPageLoader. A larger problem was the fact that the EventHandler.certificate interface method (in this case the LoadListener.certificate implementation) once per https connection instead of once per request as was documented. That meant if an https connection was reused (which happens frequently on login pages such as https://www.google.com/accounts which use the POST -> redirect -> GET idiom to avoid POST data page refresh warnings) then later pages never were associated with an SslCertificate. The solution was to change EventHandler.certificate to be called once per request, specifcally before the request. This means we no longer call the certificate method in the handleSslErrorRequest case, which is okay because it includes the SslCertificate within the SslError and that is what the BrowserActivity expects. Change-Id: Icbd9bd98c89db82762d1d06de85e1cde2470300d
/frameworks/base/core/java/android/net/http/EventHandler.java
|
4c8db8a4feb2afbd9d5f94ff09c7167ca34076c4 |
|
31-Jul-2009 |
Grace Kloba <klobag@google.com> |
Fix #2025900. If a https request is canceled while openConnection is called and a ssl error happened, the http thread can be blocked for up to 10 min. Added code to detect this case and unlock the thread.
/frameworks/base/core/java/android/net/http/EventHandler.java
|
9066cfe9886ac131c34d59ed0e2d287b0e3c0087 |
|
04-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //depot/cupcake/@135843
/frameworks/base/core/java/android/net/http/EventHandler.java
|
d83a98f4ce9cfa908f5c54bbd70f03eec07e7553 |
|
04-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //depot/cupcake/@135843
/frameworks/base/core/java/android/net/http/EventHandler.java
|
54b6cfa9a9e5b861a9930af873580d6dc20f773c |
|
21-Oct-2008 |
The Android Open Source Project <initial-contribution@android.com> |
Initial Contribution
/frameworks/base/core/java/android/net/http/EventHandler.java
|