Has anyone updated the Jaisen Mathai OAuth library to support manually
following the 301s? Since FOLLOW_LOCATION doesn't work on POSTs, the
library needs to be re-written in parts to manually follow the
redirects.
Don't want to duplicate the work if someone has done it.
The code is here:
On Sep 1, 5:00 pm, jmathai jmat...@gmail.com wrote:
I'm reconsidering adding support for POSTs. What's the usecase
exactly? Does Twitter 302 POST requests? If so, what's gained by the
application if it follows that?
Unless I am mistaken Twitter is still doing the 302 on POST as a
On Sep 1, 6:41 pm, jmathai jmat...@gmail.com wrote:
That's a valid point. What do you think of following on GETs and
throwing an exception for POSTs? Not sure many people like to deal
with exceptions (I prefer them).
It would be helpful if someone from Twitter or who has done some
extensive
