OAuth url_encode examples don't make sense


#1

I’m trying to understand the example at https://dev.twitter.com/docs/auth/oauth#Acquiring_a_request_token. It looks like the oauth_callback parameter, “http://localhost:3005/the_dance/process_callback?service_provider_id=11” is encoded as:

http%253A%252F%252Flocalhost%253A3005%252Fthe_dance%252Fprocess_callback%253Fservice_provider_id%253D11

Is this correct? It seems to me the ‘://’ should be “%3A%2F%2F”, not “%253A%252F%252F”. It looks like something took two trips through url_encode().


#2

You’re correct, this looks to be an encoding issue in the transfer to the new documentation system. I’ll fix up these examples as soon as I can. Thanks.


#3

Same for me here! I was almost changing my code to reflect this (bug).
Thanks for the explanation guys…


#4

“I’ll fix up these examples as soon as I can.” 11 weeks 3 days ago
It’s still there and the example oauth_signature is computed based on the invalid signature base string.


#5

http%253A%252F%252Flocalhost%253A3005%252Fthe_dance%252Fprocess_callback%253Fservice_provider_id%253D11