Hi Paul,
Dossy is correct on both counts. The 500 is not the ideal
response and we're working on fixing those error messages where we
can. If you can provide the request/response headers, and the response
body as well, it might help me improve the error messaging. I
understand if you don't want to send it to the whole list … feel free
to send it to me directly.
Thanks;
– Matt Sanford / @mzsanford
Twitter Dev
On Apr 27, 2009, at 2:34 PM, Dossy Shiobara wrote:
On 4/27/09 5:29 PM, Paul Kinlan wrote:
Bellow is an example query.
http://twitter.com/friendships/create.xml?screen_name=twollo&oauth_nonce=71594710&oauth_timestamp=1240867081&oauth_consumer_key=xxxx&oauth_signature_method=HMAC-SHA1&oauth_version=1.0&oauth_token=xxxxx&oauth_signature=xxxx
"s" comes after "o".
OAuth 1.0 specification mandates the parameters be sorted when the
signature is computed. Are you doing this?
Also, getting HTTP 500 Server Error ... I ran into that when I was
using HTTP Authorize header authentication and didn't "Parameter
Encode" the signature.
--
Dossy Shiobara | do...@panoptic.com | http://dossy.org/
Panoptic Computer Network | http://panoptic.com/
"He realized the fastest way to change is to laugh at your own
folly -- then you can let go and quickly move on." (p. 70)
