Thanks for quick reply.

I have corrected the request url.

Then I got the correct result.

In header I have made no change.

Thanks once again .

Regards,
George

On Thu, Jun 16, 2011 at 12:27 PM, kamesh SmartDude <
kamesh.smartd...@gmail.com> wrote:

> The Requrl u Supplied
> http://api.twitter.com/1/statuses/user_timeline.json?screen_name=***?
> page=1?include_rts=true
> is wrong. and in the headers u can remove the parameters
>
> correct one is
>
> http://api.twitter.com/1/statuses/user_timeline.json?screen_name=***&;
> page=1&include_rts=true<http://api.twitter.com/1/statuses/user_timeline.json?screen_name=***?page=1?include_rts=true>
>
> And the headers
>
> OAuth oauth_consumer_key="**",
>           oauth_nonce="PaIdH40QrMznwDjGbD75a_hRDuE7Ys",
>
>           oauth_signature_method="HMAC-SHA1",
>           oauth_timestamp="1308206637",
>           oauth_token="**",
>           oauth_version="1.0",
>           oauth_signature="YJ8LsrrXd13v0YLtnKSRdHScjaQ%3D"
>
> Here in Headers removed the screen_name, include_rts, and page parameters
>
> //kamesh
>
>
>
> On Thu, Jun 16, 2011 at 12:19 PM, Georgooty varghese 
> <georgo...@gmail.com>wrote:
>
>> Dear Twitter,
>>
>> I have found some mismatching in header value.
>>
>>
>> Rquest url is given below,
>>
>> http://api.twitter.com/1/statuses/user_timeline.json?include_rts=true&oauth_consumer_key=****&oauth_nonce=15d_Hx5zHE_9ntMQZR30RbGI6UAeZ&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1308205453&oauth_token**&oauth_version=1.0&page=1
>> &screen_name=MayuriModa9&oauth_signature=e2eZoO42zO%2B95IRf6QHhvxfnRP0%3D
>>
>> In response I got json response.
>> But in header values ,I have found,
>>
>> Status Value :200 OK
>> :X-Warning Value :Invalid OAuth credentials detected
>>
>> Its working fine. But I have a doubt, In future any problem?????????????
>>
>> So I have changed the http request to authentication mechanism to rquest
>> url to auth header.
>>
>> request url
>>
>> http://api.twitter.com/1/statuses/user_timeline.json?screen_name=***?page=1?include_rts=true
>>
>> header is given below,
>> OAuth include_rts="true",oauth_consumer_key="**",
>> oauth_nonce="PaIdH40QrMznwDjGbD75a_hRDuE7Ys",
>> oauth_signatu re_method="HMAC-SHA1",
>> oauth_timestamp="1308206637",oauth_token="**",
>> oauth_version="1.0",page="1",screen_name="****",
>> oauth_signature="YJ8LsrrXd13v0YLtnKSRdHScjaQ%3D"
>>
>>
>> But I didnt got the result
>> ,
>>
>> got 404 Not Found error.
>>
>> Please  help me to solve this issue.
>>
>> Regards,
>> Geoirge
>>
>>  --
>> Twitter developer documentation and resources:
>> https://dev.twitter.com/doc
>> API updates via Twitter: https://twitter.com/twitterapi
>> Issues/Enhancements Tracker:
>> https://code.google.com/p/twitter-api/issues/list
>> Change your membership to this group:
>> https://groups.google.com/forum/#!forum/twitter-development-talk
>>
>
>  --
> Twitter developer documentation and resources: https://dev.twitter.com/doc
> API updates via Twitter: https://twitter.com/twitterapi
> Issues/Enhancements Tracker:
> https://code.google.com/p/twitter-api/issues/list
> Change your membership to this group:
> https://groups.google.com/forum/#!forum/twitter-development-talk
>

-- 
Twitter developer documentation and resources: https://dev.twitter.com/doc
API updates via Twitter: https://twitter.com/twitterapi
Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list
Change your membership to this group: 
https://groups.google.com/forum/#!forum/twitter-development-talk

Reply via email to