doh! Thanks, Matt, I should have diagnosed that myself. it's working
now.
much obliged.

Brad


On Sep 15, 6:15 pm, themattharris <thematthar...@twitter.com> wrote:
> Hey Brad,>
> Your full request URL doesn't contain the cursor parameter. It looks
> like when you add the OAuth parameters you are dropping the cursor
> one.
> We recommend, instead of using query string or the POST body for OAuth
> paramters you instead use the authorisation header.
>
> In your case this would mean your URL would be:
>    http://api.twitter.com/1/endlesscities/urban/members.json?cursor=1343...
>
> and in your request headers you would have:
>
> Authorization: OAuth oauth_consumer_key="MgdaAGLAt4VQzGKvoczhA",
> oauth_nonce="68156293", oauth_signature="QkEP3%2BsCmz0C
> %2FdjHJcdgUyTDbuI%3D", oauth_signature_method="HMAC-SHA1",
> oauth_timestamp="1284515562", oauth_token="18904533-
> Y1BfS5tRvV7FnrynYFIoLojrL4FjrS0CUCrZbyoNx", oauth_version="1.0"
>
> Hope that helps,
> Matt
>
> On Sep 14, 7:09 pm, Brad <bdeg...@gmail.com> wrote:
>
>
>
> > Thanks, Matt,
>
> > This is the full 
> > requesthttp://api.twitter.com/1/endlesscities/urban/members.json?oauth_nonce...
>
> > doing a urllib.urlopen( ) on that.
>
> > This is the Python request object {'http_url': 'http://api.twitter.com/
> > 1/endlesscities/urban/members.json?cursor=1343981850785981701',
> > 'http_method': 'GET', 'parameters': {'oauth_nonce': '68156293',
> > 'oauth_timestamp': 1284515562, 'oauth_consumer_key':
> > 'MgdaAGLAt4VQzGKvoczhA', 'oauth_signature_method': 'HMAC-SHA1',
> > 'oauth_version': '1.0', 'oauth_token': '18904533-
> > Y1BfS5tRvV7FnrynYFIoLojrL4FjrS0CUCrZbyoNx', 'oauth_signature':
> > 'QkEP3+sCmz0C/djHJcdgUyTDbuI='}}
>
> > I get results back, so the auth is working, but the cursor stays the
> > same.
>
> > thanks for whatever insight you can give.
>
> > On Sep 14, 10:37 am, Matt Harris <thematthar...@twitter.com> wrote:
>
> > > GET works fine for this method and when I test the cursors for your
> > > list below everything works correctly. So we can work out what is
> > > going on can you share the headers you are sending to the API.
>
> > > Also, you will want to update your URLs to the correct host. The
> > > correct URL to use ishttp://api.twitter.com/1/--makingyour
> > > request:
> > >    http://api.twitter.com/1/endlesscities/urban/members.json?cursor=-1
>
> > > Best,
> > > Matt
>
> > > On Sun, Sep 12, 2010 at 6:44 PM, Brad <bdeg...@gmail.com> wrote:
> > > > maybe I'm doing something wrong, but the cursor returned from the list
> > > > members call seems to be misbehaving.
>
> > > > if I hit:
> > > >http://twitter.com/endlesscities/urban/members.json?cursor=-1
>
> > > > it returns
> > > > "next_cursor":1343981850785981701, "previous_cursor":0
>
> > > > if I pass it that new cursor:
> > > >http://twitter.com/endlesscities/urban/members.json?cursor=1343981850...
>
> > > > it returns the same thing:
> > > > "next_cursor":1343981850785981701, "previous_cursor":0
>
> > > > What's up with that? This has cropped up thanks to switching from
> > > > basic Auth to Oauth. I'm doing a GET because it won't allow me to do a
> > > > POST.
>
> > > > thanks in advance for any help.
>
> > > > --
> > > > 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?hl=en
>
> > > --
>
> > > Matt Harris
> > > Developer Advocate, Twitterhttp://twitter.com/themattharris

-- 
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?hl=en

Reply via email to