Re: [twitter-dev] The remote server returned an error: (500) Internal Server Error.
I'm migrating my shell app from basic to xAuth and now I'm getting the error from the subject. You mean The remote server returned an error: (500) Internal Server Error. ? I looked around and I found this page http://apiwiki.twitter.com/HTTP-Response-Codes-and-Errors where it says something is broken, is it? do I have an error on my app or is there an error on the twitter API? You might want to post what you're trying to access and your signature base. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- Proponents of other opinions will be merrily beaten to a bloody pulp. --
Re: [twitter-dev] The remote server returned an error: (500) Internal Server Error.
yeap, that´s right! On Tue, May 11, 2010 at 12:25, Cameron Kaiser spec...@floodgap.com wrote: I'm migrating my shell app from basic to xAuth and now I'm getting the error from the subject. You mean The remote server returned an error: (500) Internal Server Error. ? I looked around and I found this page http://apiwiki.twitter.com/HTTP-Response-Codes-and-Errors where it says something is broken, is it? do I have an error on my app or is there an error on the twitter API? You might want to post what you're trying to access and your signature base. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- Proponents of other opinions will be merrily beaten to a bloody pulp. --
Re: [twitter-dev] The remote server returned an error: (500) Internal Server Error.
Sorry, I didn´t see your request in the mail I'm trying to access https://api.twitter.com/oauth/access_token with GET as the http method... Is that ok? My signature base is: GEThttps%3A%2F%2Fapi.twitter.com %2Foauth%2Faccess_tokenoauth_consumer_key%3Dmy_consumer_key%26oauth_nonce%3DafQ4ux5qRH9GaH8tVaDCwInLy6z8snR6wiq8lKcD6s%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1273592580%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth%26x_auth_password%3Dmy_password%26x_auth_username%3Dmy_user thanks On Tue, May 11, 2010 at 12:37, sebastian gomez sebastiangomezcor...@gmail.com wrote: yeap, that´s right! On Tue, May 11, 2010 at 12:25, Cameron Kaiser spec...@floodgap.comwrote: I'm migrating my shell app from basic to xAuth and now I'm getting the error from the subject. You mean The remote server returned an error: (500) Internal Server Error. ? I looked around and I found this page http://apiwiki.twitter.com/HTTP-Response-Codes-and-Errors where it says something is broken, is it? do I have an error on my app or is there an error on the twitter API? You might want to post what you're trying to access and your signature base. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- Proponents of other opinions will be merrily beaten to a bloody pulp. --
Re: [twitter-dev] The remote server returned an error: (500) Internal Server Error.
Sorry, I didn__t see your request in the mail I'm trying to access https://api.twitter.com/oauth/access_token with GET as the http method... Is that ok? My signature base is: GEThttps%3A%2F%2Fapi.twitter.com %2Foauth%2Faccess_tokenoauth_consumer_key%3Dmy_consumer_key%26oauth_nonce%3DafQ4ux5qRH9GaH8tVaDCwInLy6z8snR6wiq8lKcD6s%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1273592580%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth%26x_auth_password%3Dmy_password%26x_auth_username%3Dmy_user It should be POST. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- Communism doesn't work because people like to own stuff. -- Frank Zappa
Re: [twitter-dev] The remote server returned an error: (500) Internal Server Error.
Ok, when I uset POST I get a 401 (Unauthorized) :( I guess I'm doing something wrong... what could it be? is my base string ok? On Tue, May 11, 2010 at 12:47, Cameron Kaiser spec...@floodgap.com wrote: Sorry, I didn__t see your request in the mail I'm trying to access https://api.twitter.com/oauth/access_token with GET as the http method... Is that ok? My signature base is: GEThttps%3A%2F%2Fapi.twitter.com %2Foauth%2Faccess_tokenoauth_consumer_key%3Dmy_consumer_key%26oauth_nonce%3DafQ4ux5qRH9GaH8tVaDCwInLy6z8snR6wiq8lKcD6s%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1273592580%26oauth_version%3D1.0%26x_auth_mode%3Dclient_auth%26x_auth_password%3Dmy_password%26x_auth_username%3Dmy_user It should be POST. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- Communism doesn't work because people like to own stuff. -- Frank Zappa
Re: [twitter-dev] The remote server returned an error: (500) Internal Server Error.
Ok, when I uset POST I get a 401 (Unauthorized) :( I guess I'm doing something wrong... what could it be? is my base string ok? The server should give you a message like Invalid nonce or Invalid signature or some such. If you don't even get that, I suspect your xAuth access is not working or set up. Mail a...@twitter.com. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- BOND THEME NOW PLAYING: Diamonds Are Forever -
Re: [twitter-dev] The remote server returned an error: (500) Internal Server Error.
will do that, thanks On Tue, May 11, 2010 at 12:53, Cameron Kaiser spec...@floodgap.com wrote: Ok, when I uset POST I get a 401 (Unauthorized) :( I guess I'm doing something wrong... what could it be? is my base string ok? The server should give you a message like Invalid nonce or Invalid signature or some such. If you don't even get that, I suspect your xAuth access is not working or set up. Mail a...@twitter.com. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- BOND THEME NOW PLAYING: Diamonds Are Forever -
Re: [twitter-dev] The remote server returned an error: (500) Internal Server Error.
Sebastian, Also make sure that all of the following points are true in your implementation: * You are using POST * You are using SSL * Your xAuth parameters are the ONLY parameters in your POST body * You're setting a Content-Type header of application/x-www-form-urlencoded * Your xAuth parameters are properly part of your signature base string, where they will appear at the end of the signature base string in alphabetical order * You're using HTTP header-based OAuth -- not attaching OAuth parameters to the URL or POST body * You're HTTP Authorization header should only have oauth_* parameters in it, not any of the xauth parameters Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Tue, May 11, 2010 at 9:07 AM, sebastian gomez sebastiangomezcor...@gmail.com wrote: will do that, thanks On Tue, May 11, 2010 at 12:53, Cameron Kaiser spec...@floodgap.comwrote: Ok, when I uset POST I get a 401 (Unauthorized) :( I guess I'm doing something wrong... what could it be? is my base string ok? The server should give you a message like Invalid nonce or Invalid signature or some such. If you don't even get that, I suspect your xAuth access is not working or set up. Mail a...@twitter.com. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- BOND THEME NOW PLAYING: Diamonds Are Forever -
Re: [twitter-dev] The remote server returned an error: (500) Internal Server Error.
Got it! I was using my consumer key to create signature instead of the secret :S thanks all! On Tue, May 11, 2010 at 13:54, sebastian gomez sebastiangomezcor...@gmail.com wrote: Great help Taylor thanks... Will check on that and come back to you. thanks again On Tue, May 11, 2010 at 13:20, Taylor Singletary taylorsinglet...@twitter.com wrote: Sebastian, Also make sure that all of the following points are true in your implementation: * You are using POST * You are using SSL * Your xAuth parameters are the ONLY parameters in your POST body * You're setting a Content-Type header of application/x-www-form-urlencoded * Your xAuth parameters are properly part of your signature base string, where they will appear at the end of the signature base string in alphabetical order * You're using HTTP header-based OAuth -- not attaching OAuth parameters to the URL or POST body * You're HTTP Authorization header should only have oauth_* parameters in it, not any of the xauth parameters Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Tue, May 11, 2010 at 9:07 AM, sebastian gomez sebastiangomezcor...@gmail.com wrote: will do that, thanks On Tue, May 11, 2010 at 12:53, Cameron Kaiser spec...@floodgap.comwrote: Ok, when I uset POST I get a 401 (Unauthorized) :( I guess I'm doing something wrong... what could it be? is my base string ok? The server should give you a message like Invalid nonce or Invalid signature or some such. If you don't even get that, I suspect your xAuth access is not working or set up. Mail a...@twitter.com. -- personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com -- BOND THEME NOW PLAYING: Diamonds Are Forever -
