One other thing that I can think of, since that actually affects our
own app too (need to finally fix this...), is retrying requests.
Commons HTTP has a built-in request-retry logic, which will resend
"safe" HTTP requests (i.e. idempotent requests such as GET or PUT).
This does NOT work with OAuth, since the server will treat this as a
replay attack (nonce and timestamp will be the same) and drop the
request with a 401.
You said you're not using Apache Commons HTTP, but double check your
On Mon, Jun 11, 2012 at 9:20 PM, Paddy Foran <foran.pa...@gmail.com> wrote:--
> I've used the library for years in a rather popular application, and it has
> proven its mettle on pretty much every device and OS level.
> If I had to take a guess, based on personal experience, I would bet that the
> On Mon, Jun 11, 2012 at 3:09 PM, Matthias Käppler
>> I doubt this would be related to the library. The lib is not concerned
>> I don't know, could be many things. We use the library on all versions
>> On Mon, Jun 11, 2012 at 9:03 PM, Warren McAllister
>> > DefaultOauthConsumer advice still holds?
>> > Warren
>> > On Monday, 11 June 2012 19:12:35 UTC+1, Matthias wrote:
>> >> don't use DefaultOAuthConsumer on Android
>> >> On Monday, June 11, 2012 6:37:22 PM UTC+2, Warren McAllister wrote:
>> >>> Hello everyone, I'm trying to get Oauth signing to work, as the title
>> >>> Any help or debugging tips much appreciated - code snippet follows:
>> >>> OAuthConsumer consumer = new DefaultOAuthConsumer(CONSUMER_KEY,
>> >>> connection = (HttpURLConnection)url.openConnection();
>> >>> connection.setRequestMethod("GET");
>> > --
>> > To post to this group, send email to firstname.lastname@example.org.
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.