In 3 legged oauth, "/oauth/authorize" redirect to twitter.com


#1

Hi,
While using 3 legged oauth , user get redirect to twitter.com instead of oauth_callback. Which is causing oauth process to fail as we are not getting access token.

This used to work before. I checked and we are following every steps of 3-legged authorization.

Any Idea why this is happening and if I am suppose to change something.
Thanks
Nikhil

Edit:- I have noticed that this problem comes only when I add urleoncoded json params in ‘oauth_callback’. For normal value it works.
For example it works if I pass oauth_callback as :-
http://192.168.1.7:8080/token?a=hello&b=3

it doesn’t work if I pass urlencoded json value in oauth_callback:-
http://192.168.1.7:8080/token?twitter={‘a’%3A+‘hello’%2C+‘b’%3A+3}

I think it is some recent development as second case used to work before.