Ok. Thanks Tom. What wrong I have made in this. I didn't find any issue. Could u please check the issue. I am waiting for your reply.
Regards, George On Thu, Dec 16, 2010 at 1:58 PM, Tom van der Woerdt <[email protected]> wrote: > They look fine, and since the rest of the requests work fine (which you > said), I have to assume that it's not the signature generation. Also, since > you're not the only one to mention this in the past 12 hours, I have to > leave open the possibility of Twitter being the issue. > > However, before looking at that, please double check that the Base String > matches what you are actually doing! > > Tom > > > > > On 12/16/10 7:25 AM, Georgooty varghese wrote: > >> >> Thanks twitter for your quick reply. >> >> I have make only one modification into my code. Other code changes do >> only when I get your reply. >> I have changed url for user time line http to https. >> >> Here I have copied my user time line base url and signature and base >> string. Please suggest to me a correct way for this. >> >> *Base URL* >> >> :oauth_consumer_key=*****************&oauth_nonce=EF2k_xwovJInFfq&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1292480095&oauth_token=*****************************************&oauth_version=1.0&page=1&screen_name=Sanoop_SP >> >> >> * >> Signature*:FcKenujneOtQklp6HZYDkRc7BYzelW9Fsadj324RE&pV1owATZgqcsx3R6FaM0qGilyBRkkP95zwNVosGoSnc >> >> >> *Base string*:GET&https%3A%2F%2Fapi.twitter.com >> <http://2Fapi.twitter.com >> >%2F1%2Fstatuses%2Fuser_timeline.json&oauth_consumer_key%****************%26oauth_nonce%3DEF2k_xwovJInFfq%26oauth_signature_method%3DHMAC-SHA1%26oauth_timestamp%3D1292480095%26oauth_token%**************%26oauth_version%3D1.0%26page%3D1%26screen_name%3DSanoop_SP >> >> >> >> >> What mistake I have made in this. >> >> Please reply. >> >> I am waiting for your reply. >> >> Regards, >> George >> >> >> >> On Wed, Dec 15, 2010 at 11:21 PM, Tom van der Woerdt <[email protected] >> <mailto:[email protected]>> wrote: >> >> Hi George, >> >> There have been some changes to Twitter's API and while not all of >> them have been "activated" yet, some of them may apply to you. >> >> "Incorrect signature" usually means that your signature is bad. This >> can mean a lot of things, but if only your user_timeline part is >> broken, you can start by looking at these : >> * Make sure that the URL in the Base String does not contain the >> query part of an URL (= anything after (and including) the ? part of >> the URL) >> - Good: https://api.twitter.com/1/statuses/user_timeline.json >> - Bad: >> https://api.twitter.com/1/statuses/user_timeline.json?count=200 >> Of course, this only applies to the Base String. Making a GET >> request is still fine. >> * Make sure that you specify the correct method in the Base String. >> - If you are making a GET request, put GET in the Base String. >> * Make sure that you properly URL-encode all values in the Base >> String >> - Good: Hello%20Twitter >> - Bad: Hello+Twitter >> - (This does not really apply to user_timeline) >> >> If you checked the above and the issue is still there, please show >> us a sample Base String and a dump of the request you make to the >> Twitter API. >> >> Tom >> >> >> >> >> On 12/15/10 6:06 PM, Georgooty varghese wrote: >> >> Dear Twitter, >> >> I have been created a twitter application. I got xauth token for my >> application. I have implemented twitter functionalities like home >> tweets, user info, follower details, following details, user >> time line. >> These functionalities working smoothly. Also get each user time >> line . But >> Todat, usser time url is not working right now. I got incorrect >> signature exception.. >> >> Though usertime line qury is not working yesterday. I have no >> change any >> line code. >> If any change need to my coding? >> >> >> >> Anybody please help me.. >> >> I am waiting for your reply. >> >> Regards, >> George >> >> -- >> Twitter developer documentation and resources: >> http://dev.twitter.com/doc >> API updates via Twitter: http://twitter.com/twitterapi >> Issues/Enhancements Tracker: >> http://code.google.com/p/twitter-api/issues/list >> Change your membership to this group: >> http://groups.google.com/group/twitter-development-talk >> >> >> -- >> Twitter developer documentation and resources: >> http://dev.twitter.com/doc >> API updates via Twitter: http://twitter.com/twitterapi >> Issues/Enhancements Tracker: >> http://code.google.com/p/twitter-api/issues/list >> Change your membership to this group: >> http://groups.google.com/group/twitter-development-talk >> >> >> -- >> Twitter developer documentation and resources: http://dev.twitter.com/doc >> API updates via Twitter: http://twitter.com/twitterapi >> Issues/Enhancements Tracker: >> http://code.google.com/p/twitter-api/issues/list >> Change your membership to this group: >> http://groups.google.com/group/twitter-development-talk >> > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk
