On Sat, Nov 19, 2011 at 7:14 PM, DoubleCheese <[email protected]> wrote:
> Thanks for the reply, I am already using a WebViewClient here
> (ThisWebViewClient).
I noticed that about five seconds after pressing Send... :-)
> However, what I've noticed is that the shouldOverrideUrlLoading()
> seems to be not getting the right hostname and my theory is that the
> 302 processing has already happened before the
> shouldOverrideUrlLoading() is called.
>
> Basically this is what happens:
> 1) I call webView.loadUrl("http://host1/somePath/?param=eg";); - this
> should redirect to "http://host2/path2/?otherparam=eg";
> 2) When shouldOverrideUrlLoading() is called the url parameter passed
> is not correct and it seems to change it to "http://host2/somePath/?
> param=eg"
Can you check the server logs and see what is happening from that side?
I'm not aware of much else for tailoring redirect behavior. You might
dump getOriginalUrl() on the WebView to see what it reports.
--
Mark Murphy (a Commons Guy)
http://commonsware.com | http://github.com/commonsguy
http://commonsware.com/blog | http://twitter.com/commonsguy
_The Busy Coder's Guide to Android Development_ Version 3.6 Available!
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
