You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A common omission in certificate pinning implementations and discussions seems to be coverage for WebView requests. Are there plans to provide a sample WebViewClient implementation that invokes the pinning code to make secure requests so developers will know how to do this securely?
The text was updated successfully, but these errors were encountered:
Great Question - The only method I've seen is implementing shouldinterceptrequest and handling the connections through your pinning implementation and passing back data :-/
I've seen that, however, shouldInterceptRequest is Synchronous and this would force all web requests to be synchronous in order to be able to supply the data in the return value of this method, as far as I can tell. Not sure what the performance implications of that would be for a typical webview - would there be blocking on the thread? Of course, there is also the caveat that this excludes all older Android OSes (before Honeycomb), although there's good reason to exclude those anyhow.
A common omission in certificate pinning implementations and discussions seems to be coverage for WebView requests. Are there plans to provide a sample WebViewClient implementation that invokes the pinning code to make secure requests so developers will know how to do this securely?
The text was updated successfully, but these errors were encountered: