On Mon, Oct 25, 2010 at 11:28 PM, themattharris
wrote:
> Hey everyone,
>
> So OAuth encoding can get confusing and lead to situations like this
> so i'll go through a very verbose walkthrough to hopefully explain how
> it all works.
First, thank you for taking the time to post this, I agree OAuth
Hey everyone,
So OAuth encoding can get confusing and lead to situations like this
so i'll go through a very verbose walkthrough to hopefully explain how
it all works.
The key section of the specification explaining this part is
3.4.1.3.2:
http://tools.ietf.org/html/rfc5849#section-3.4.1.3.2
Correct, I still had the issue when escaping "track=...". Escaping
params individually did not work either. Still able to tweet though...
Maybe it is a hint at the trouble being more/different than double
encoding?
Cheers,
Bradley
On Oct 25, 4:59 pm, Ciaran wrote:
> On Mon, Oct 25, 2010 at 10:53
On Mon, Oct 25, 2010 at 10:53 PM, bradley.meck wrote:
> So in my case i just encodeURIComponent somewhere? I tried on the POST
> params and it did not work, nor did the 4 permutations of api-key/
> secret and access-token-key/secret.
Odd, Escaping "track="+tracking.join(",")+"&count=0" should wor
So in my case i just encodeURIComponent somewhere? I tried on the POST
params and it did not work, nor did the 4 permutations of api-key/
secret and access-token-key/secret.
.
On Oct 25, 4:31 pm, Ciaran wrote:
> Hey Bradley,
>
> This is another instance of the the ongoing (and as yet un-answered
>
