That's simply for generating the signature base string. it does not matter when you're actually sending the parameters.
On Wed, Oct 7, 2009 at 05:33, ryan alford <ryanalford...@gmail.com> wrote: > Here is the documentation on ordering the parameters... > http://oauth.net/core/1.0#anchor14 > > Section 9.1.1 > > Parameters are sorted by name, using lexicographical byte value ordering. > If two or more parameters share the same name, they are sorted by their > value. > > This is excluding the oauth_signature parameter. > > Ryan > <http://oauth.net/core/1.0/#auth_step3> > > On Wed, Oct 7, 2009 at 6:11 AM, ryan alford <ryanalford...@gmail.com>wrote: > >> Yes, the order does matter. All parameters need to be in order except >> for the signature. The signature should be last and should have been >> generated with all of the parameters in the correct order. >> >> >> >> On Oct 7, 2009, at 12:10 AM, jmathai <jmat...@gmail.com> wrote: >> >> > >> > The order of parameters shouldn't matter. What library are you using >> > to generate the url? >> > >> > On Oct 6, 8:51 pm, ryan alford <ryanalford...@gmail.com> wrote: >> >> The signature needs to be at the end of the URL, not sorted with the >> >> other parameters. >> >> >> >> On Oct 6, 2009, at 11:47 PM, uooooookeng <loque1...@nate.com> wrote: >> >> >> >> >> >> >> >>> I am trying to run a sample app >> >>> but i am getting 401 error during request_token phase. >> >> >> >>> Failed to validate oauth signature and token >> >> >> >>> this is what i am accessing: >> >> >> >>> http://twitter.com/oauth/request_token?oauth_consumer_key=HiQ2WSsefHS >> >>> ... >> >> >> >>> What's problem this sentence.... >> >>> Anybody help me plz.. >> > > -- Internets. Serious business.
