Thank you for the idea. Though, I don't think it will work. What about AJAX, objects, images requests? I assume shouldInterceptRequest isn't called for these.
Krystian W dniu sobota, 13 grudnia 2014 22:14:33 UTC+1 użytkownik Doug napisał: > > You could use a WebViewClient to intercept everything a WebView is trying > to fetch and fetch it yourself using whatever API suits your needs. > > Doug > > On Friday, December 12, 2014 12:15:35 PM UTC-8, Krystian Lewandowski wrote: >> >> Hi, >> I'm trying to update ConnectivityManager.requestRouteToHost >> implementation from deprecated one to ConnectivityManager.requestNetwork >> introduced in Lollipop. It supports Sockets, SocketFactories, >> URLConnections - this is fine. The only thing missing at the moment is >> WebView support. Application's requirement is to route WebView.loadUrl >> requests via specific interface, but I can't see how it could be done with >> the new API (I can't use setProcessDefaultNetwork). >> >> I looked at WebView API but couldn't find anything new that would support >> changed routing API. Is it supported, am I missing something? >> >> Thank you, >> Krystian >> > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to android-developers+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
