Received: by 10.150.47.32 with SMTP id u32mr3529241ybu.11.1276717995736;
Wed, 16 Jun 2010 12:53:15 -0700 (PDT)
X-BeenThere: twitter-development-talk@googlegroups.com
Received: by 10.151.33.42 with SMTP id l42ls394326ybj.1.p; Wed, 16 Jun 2010
12:53:04 -0700 (PDT)
Received: by 10.150.252.11 with SMTP id z11mr3545891ybh.3.1276717983970;
Wed, 16 Jun 2010 12:53:03 -0700 (PDT)
Received: by 10.150.252.11 with SMTP id z11mr3545887ybh.3.1276717983914;
Wed, 16 Jun 2010 12:53:03 -0700 (PDT)
Return-Path: <taylorsinglet...@twitter.com>
Received: from mail-gw0-f45.google.com (mail-gw0-f45.google.com [74.125.83.45])
by gmr-mx.google.com with ESMTP id 19si390875ywh.8.2010.06.16.12.53.03;
Wed, 16 Jun 2010 12:53:03 -0700 (PDT)
Received-SPF: pass (google.com: domain of taylorsinglet...@twitter.com designates 74.125.83.45 as permitted sender) client-ip=74.125.83.45;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of taylorsinglet...@twitter.com designates 74.125.83.45 as permitted sender) smtp.mail=taylorsinglet...@twitter.com
Received: by gwaa20 with SMTP id a20so2419999gwa.18
for <twitter-development-talk@googlegroups.com>; Wed, 16 Jun 2010 12:53:03 -0700 (PDT)
Received: by 10.224.88.234 with SMTP id b42mr4719318qam.276.1276717982892;
Wed, 16 Jun 2010 12:53:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.224.19.130 with HTTP; Wed, 16 Jun 2010 12:52:42 -0700 (PDT)
In-Reply-To: <ccb51ce1-1edf-423b-9611-dcd7355da56e@k39g2000yqb.googlegroups.com>
References: <d3e6c422-29ce-4d54-862f-9407671d4c87@c10g2000yqi.googlegroups.com>
<-5348290580678020998@unknownmsgid> <202d09e1-93bc-4ffe-b0a1-3b5bdee101b0@y4g2000yqy.googlegroups.com>
<24b8f9b1-54ef-4280-ac71-269a2d446c54@k39g2000yqb.googlegroups.com>
<97827ba6-2fe7-478a-84d7-cbbf7b60c955@z8g2000yqz.googlegroups.com>
<14071413-547a-42de-a1a1-7312f3b6667f@q12g2000yqj.googlegroups.com>
<AANLkTimO2R_xFzWhPcRL8dDK9P7JppRy-5Yysi5ABL80@mail.gmail.com>
<ae8613a5-1cae-4731-b5db-0770e86f591d@y4g2000yqy.googlegroups.com>
<ccb51ce1-1edf-423b-9611-dcd7355da...@k39g2000yqb.googlegroups.com>
From: Taylor Singletary <taylorsinglet...@twitter.com>
Date: Wed, 16 Jun 2010 12:52:42 -0700
Message-ID: <AANLkTinFjCuUVe_MEFpLyrS1lUddd5prC3tNMjQIN...@mail.gmail.com>
Subject: Re: [twitter-dev] Re: oauth status update returning error 401 invalid
/ used nonce
To: twitter-development-talk@googlegroups.com
Content-Type: multipart/alternative; boundary=00c09f905ff3da547a04892b112e
--00c09f905ff3da547a04892b112e
Content-Type: text/plain; charset=UTF-8
Our setup is such that I can't easily trace a single request.
Connecting some dots: if you have time, can you try to use a different
access token with your keys and see if it has the ability to tweet?
Can you go to your application settings and verify that your application is
in "read/write mode" on dev.twitter.com?
Finally, this might be a case of something funky with your client
application -- which might be resolved by creating a new one. But let's rule
out some other possibilities first.
Taylor Singletary
Developer Advocate, Twitter
http://twitter.com/episod
On Wed, Jun 16, 2010 at 12:39 PM, Craig <chanson9...@gmail.com> wrote:
> By the way, even when I try to tweet with just one word like: "tweet",
> it doesn't work. Just simple ascii characters. Is there any way you
> can just intercept one of my test tweets and look at what, if anything
> might be going wrong on the server side?
>
> -Craig
>
>
> On Jun 16, 3:05 pm, Craig <chanson9...@gmail.com> wrote:
> > My signature base string status pair looks like:
> > status%3Dmy%2520tweet
> >
> > When I tried xAuth authentication with a * character in the password,
> > it didn't work at first. But once I double url encoded it, I was able
> > to authenticate no problem. So that definitely helps. I am now
> > double url encoding the username and password values.
> >
> > However, the tweet still didn't work. I am double url encoding the
> > status message in the signature base string and single url encoding it
> > in the post body.
> >
> > Thanks,
> > Craig
> >
> > On Jun 16, 11:30 am, Taylor Singletary <taylorsinglet...@twitter.com>
> > wrote:
> >
> >
> >
> > > Hi Craig,
> >
> > > Do you know if the status update, status=my%20tweet is being encoded
> > > correctly in your signature base string (which is the string used to
> create
> > > your signature).
> >
> > > For the signature base string, the key/value pair would look like:
> >
> > > status%3Dmy%2520tweet
> >
> > > Have you tried your xAuth authentication with spaces and other possible
> odd
> > > characters yet in fields like the password?
> >
> > > Taylor
> >
> > > On Wed, Jun 16, 2010 at 8:21 AM, Craig <chanson9...@gmail.com> wrote:
> > > > Hi Matt,
> >
> > > > Thanks for responding. My authorization header is still the same as
> > > > it was in my first message above. Here it is for another request I
> > > > just tried:
> >
> > > > OAuth oauth_nonce="TEeSMm8q3m5abhmppain",
> oauth_signature_method="HMAC-
> > > > SHA1", oauth_timestamp="1276701304",
> > > > oauth_consumer_key="xxxxxxxxxxxxxxxxx", oauth_token="xxxxxxxx-
> > > > xxxxxxxxxxxxxxxxxxxxxxxxx", oauth_signature="xxxxxxxxxxxxxxxxxxxxxxx
> > > > %3D", oauth_version="1.0"
> >
> > > > The post body is simply:
> > > > status=my%20tweet
> >
> > > > When I create the request in objective c, it looks like this: (where
> > > > authHeader is the authorization header noted above and postBody is
> the
> > > > post body noted above):
> >
> > > > NSString* requestString= [NSString
> > > > stringWithFormat:@"%@",TWITTER_STATUS_UPDATE_URL];
> > > > NSMutableURLRequest* request = [[NSMutableURLRequest alloc]
> > > > initWithURL:[NSURL
> > > > URLWithString:requestString]
> >
> > > > cachePolicy:NSURLRequestReloadIgnoringCacheData
> > > > timeoutInterval:30.0];
> > > > [request setHTTPMethod:@"POST"];
> > > > [request addValue:authHeader forHTTPHeaderField:@"Authorization"];
> > > > [request setValue:@"application/x-www-form-urlencoded"
> > > > forHTTPHeaderField:@"Content-Type"];
> > > > [request setValue:postBodyLength forHTTPHeaderField:@"Content-
> > > > Length"];
> > > > [request setHTTPBody:[postBody
> > > > dataUsingEncoding:NSUTF8StringEncoding]];
> >
> > > > This type of formatting works just fine for my xAuth authentication.
> >
> > > > On Jun 15, 4:44 pm, themattharris <thematthar...@twitter.com> wrote:
> > > > > Hey Craig,
> >
> > > > > Could you let us see what the authorization header you are sending
> > > > > looks like (obfuscating your oauth keys and secrets)?
> >
> > > > > What you're aiming for is a header similar to this:
> >
> > > > > POST /1/statuses/update.xml HTTP/1.1
> > > > > Accept: */*
> > > > > Connection: close
> > > > > User-Agent: OAuth gem v0.4.0
> > > > > Content-Type: application/x-www-form-urlencoded
> > > > > Authorization: OAuth
> > > > > oauth_consumer_key=\"xxxxxxxxxxxxxxxxxxxxxxxx\",
> > > > > oauth_nonce=\"xxxxxxxxxxxxxxxxxxxxxxxxxxxx\",
> > > > > oauth_signature=\"xxxxxxxxxxxxxxxxxxxxxxxx\",
> > > > > oauth_signature_method=\"HMAC-SHA1\",
> > > > > oauth_timestamp=\"1276634179\",
> > > > > oauth_token=\"xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx\",
> > > > > oauth_version=\"1.0\"
> > > > > Content-Length: 27
> > > > > Host: api.twitter.com
> >
> > > > > With your post body being the status you are sending. Similar to:
> >
> > > > > status=something%20to%20say
> >
> > > > > Matt
> >
> > > > > On Jun 13, 8:32 pm, Craig <chanson9...@gmail.com> wrote:
> >
> > > > > > Ok, so I believe my signature is correct because if I take out
> the
> > > > > > oauth_token parameter from the signature base I get an incorrect
> > > > > > signature error instead of the invalid/used nonce error. I am
> > > > > > definitely posting to the correct url: "
> https://api.twitter.com/1/
> > > > > > statuses/update.xml" because if I change it I get an invalid url
> > > > > > response. The nonce I'm generating is unique for every request
> I'm
> > > > > > sending. The timestamp is accurate to the number of seconds that
> have
> > > > > > passed since unix epoch. Obviously the invalid/used nonce error
> is
> > > > > > garbage.
> >
> > > > > > Here's the formatting of my URL request in obj c:
> >
> > > > > > // Create the request
> > > > > > NSString* requestString= [NSString
> > > > > > stringWithFormat:@"%@",TWITTER_STATUS_UPDATE_URL];
> > > > > > NSMutableURLRequest* request = [[NSMutableURLRequest alloc]
> > > > > > initWithURL:[NSURL
> > > > URLWithString:requestString]
> >
> > > > cachePolicy:NSURLRequestReloadIgnoringCacheData
> > > > > > timeoutInterval:30.0];
> > > > > > [request setHTTPMethod:@"POST"];
> > > > > > [request addValue:authHeader forHTTPHeaderField:@
> "Authorization"];
> > > > > > [request setValue:@"application/x-www-form-urlencoded"
> > > > > > forHTTPHeaderField:@"Content-Type"];
> > > > > > [request setValue:postBodyLength forHTTPHeaderField:@"Content-
> > > > > > Length"];
> > > > > > [request setHTTPBody:[postBody
> > > > > > dataUsingEncoding:NSUTF8StringEncoding]];
> >
> > > > > > Any other ideas? I'm at a total loss as to why this might be
> > > > > > happening.
> >
> > > > > > Thanks,
> > > > > > Craig
> >
> > > > > > On Jun 13, 3:42 pm, Craig <chanson9...@gmail.com> wrote:
> >
> > > > > > > No dice. I just tried creating a new app and using the new
> > > > keys/token
> > > > > > > to tweet. I'll go over my steps once more and see if I can
> track
> > > > down
> > > > > > > an issue somewhere...
> >
> > > > > > > On Jun 11, 8:53 pm, Taylor Singletary <
> taylorsinglet...@twitter.com>
> > > > > > > wrote:
> >
> > > > > > > > xAuth in this case, I think, is unrelated to the issue. If
> you can
> > > > use
> > > > > > > > a different key and use the "my token" feature to get your
> access
> > > > > > > > token, then try to tweet using that token, it will
> sufficiently
> > > > > > > > express the problem I think.
> >
> > > > > > > > Taylor
> >
> > > > > > > > On Jun 11, 2010, at 2:48 PM, Craig <chanson9...@gmail.com>
> wrote:
> >
> > > > > > > > > Hello,
> >
> > > > > > > > > I have an iphone app that is using xauth. I am able to
> obtain
> > > > the
> > > > > > > > > access token with no problem at all. When I go to post a
> status
> > > > > > > > > update, I receive an invalid / used nonce error. It can't
> > > > actually be
> > > > > > > > > a used nonce since I have checked this multiple times.
> Here are
> > > > the
> > > > > > > > > details of the post:
> >
> > > > > > > > > url:
> > > > > > > > >http://api.twitter.com/1/statuses/update.xml
> >
> > > > > > > > > signature base string:
> > > > > > > > > POST&http%3A%2F%2Fapi.twitter.com%2F1%2Fstatuses
> > > > > > > > >
> %2Fupdate.xml&oauth_consumer_key%3Dmyconsumerkey%26oauth_nonce
> > > > > > > > > %3D397vi5Ug1YHC3UAVUAoB%26oauth_signature_method%3DHMAC-
> > > > > > > > > SHA1%26oauth_timestamp%3D1276292596%26oauth_token%3Dmytoken
> > > > > > > > > %26oauth_version%3D1.0%26status%3Dmy%2520tweet
> >
> > > > > > > > > Authorization header:
> > > > > > > > > OAuth oauth_nonce="397vi5Ug1YHC3UAVUAoB",
> > > > oauth_signature_method="HMAC-
> > > > > > > > > SHA1", oauth_timestamp="1276292596",
> > > > > > > > > oauth_consumer_key="myconsumerkey", oauth_token="mytoken",
> > > > > > > > > oauth_signature="yOh2zQPGDBlVEP5cDWhjddQWTLc%3D",
> > > > oauth_version="1.0"
> >
> > > > > > > > > Content-Type:
> > > > > > > > > [request setValue:@"application/x-www-form-urlencoded"
> > > > > > > > > forHTTPHeaderField:@"Content-Type"];
> >
> > > > > > > > > I can see no reason why this shouldn't work. Any help
> would be
> > > > > > > > > greatly appreciated!
> >
> > > > > > > > > Thanks,
> > > > > > > > > Craig
>
--00c09f905ff3da547a04892b112e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Our setup is such that I can't easily trace a single request.<div><br><=
/div><div>Connecting some dots: if you have time, can you try to use a diff=
erent access token with your keys and see if it has the ability to tweet?</=
div>
<div><br></div><div>Can you go to your application settings and verify that=
your application is in "read/write mode" on <a href=3D"http://de=
v.twitter.com">dev.twitter.com</a>?</div><div><br></div><div>Finally, this =
might be a case of something funky with your client application -- which mi=
ght be resolved by creating a new one. But let's rule out some other po=
ssibilities first.</div>
<div><br></div><div>Taylor Singletary<br>Developer Advocate, Twitter<br><a =
href=3D"http://twitter.com/episod">http://twitter.com/episod</a><br>
<br><br><div class=3D"gmail_quote">On Wed, Jun 16, 2010 at 12:39 PM, Craig =
<span dir=3D"ltr"><<a href=3D"mailto:chanson9...@gmail.com">chanson9000@=
gmail.com</a>></span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
By the way, even when I try to tweet with just one word like: "tweet&q=
uot;,<br>
it doesn't work. =C2=A0Just simple ascii characters. =C2=A0Is there any=
way you<br>
can just intercept one of my test tweets and look at what, if anything<br>
might be going wrong on the server side?<br>
<font color=3D"#888888"><br>
-Craig<br>
</font><div><div></div><div class=3D"h5"><br>
<br>
On Jun 16, 3:05=C2=A0pm, Craig <<a href=3D"mailto:chanson9...@gmail.com"=
>chanson9...@gmail.com</a>> wrote:<br>
> My signature base string status pair looks like:<br>
> status%3Dmy%2520tweet<br>
><br>
> When I tried xAuth authentication with a * character in the password,<=
br>
> it didn't work at first. =C2=A0But once I double url encoded it, I=
was able<br>
> to authenticate no problem. =C2=A0So that definitely helps. =C2=A0I am=
now<br>
> double url encoding the username and password values.<br>
><br>
> However, the tweet still didn't work. =C2=A0I am double url encodi=
ng the<br>
> status message in the signature base string and single url encoding it=
<br>
> in the post body.<br>
><br>
> Thanks,<br>
> Craig<br>
><br>
> On Jun 16, 11:30=C2=A0am, Taylor Singletary <<a href=3D"mailto:tayl=
orsinglet...@twitter.com">taylorsinglet...@twitter.com</a>><br>
> wrote:<br>
><br>
><br>
><br>
> > Hi Craig,<br>
><br>
> > Do you know if the status update, status=3Dmy%20tweet is being en=
coded<br>
> > correctly in your signature base string (which is the string used=
to create<br>
> > your signature).<br>
><br>
> > For the signature base string, the key/value pair would look like=
:<br>
><br>
> > status%3Dmy%2520tweet<br>
><br>
> > Have you tried your xAuth authentication with spaces and other po=
ssible odd<br>
> > characters yet in fields like the password?<br>
><br>
> > Taylor<br>
><br>
> > On Wed, Jun 16, 2010 at 8:21 AM, Craig <<a href=3D"mailto:chan=
son9...@gmail.com">chanson9...@gmail.com</a>> wrote:<br>
> > > Hi Matt,<br>
><br>
> > > Thanks for responding. =C2=A0My authorization header is stil=
l the same as<br>
> > > it was in my first message above. =C2=A0Here it is for anoth=
er request I<br>
> > > just tried:<br>
><br>
> > > OAuth oauth_nonce=3D"TEeSMm8q3m5abhmppain", oauth_=
signature_method=3D"HMAC-<br>
> > > SHA1", oauth_timestamp=3D"1276701304",<br>
> > > oauth_consumer_key=3D"xxxxxxxxxxxxxxxxx", oauth_to=
ken=3D"xxxxxxxx-<br>
> > > xxxxxxxxxxxxxxxxxxxxxxxxx", oauth_signature=3D"xxx=
xxxxxxxxxxxxxxxxxxxx<br>
> > > %3D", oauth_version=3D"1.0"<br>
><br>
> > > The post body is simply:<br>
> > > status=3Dmy%20tweet<br>
><br>
> > > When I create the request in objective c, it looks like this=
: (where<br>
> > > authHeader is the authorization header noted above and postB=
ody is the<br>
> > > post body noted above):<br>
><br>
> > > NSString* requestString=3D [NSString<br>
> > > stringWithFormat:@"%@",TWITTER_STATUS_UPDATE_URL];=
<br>
> > > NSMutableURLRequest* request =3D [[NSMutableURLRequest alloc=
]<br>
> > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0initWithURL:[NSURL<br>
> > > URLWithString:requestString]<br>
><br>
> > > cachePolicy:NSURLRequestReloadIgnoringCacheData<br>
> > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0timeoutIn=
terval:30.0];<br>
> > > [request setHTTPMethod:@"POST"];<br>
> > > [request addValue:authHeader forHTTPHeaderField:@"Autho=
rization"];<br>
> > > [request setValue:@"application/x-www-form-urlencoded&q=
uot;<br>
> > > forHTTPHeaderField:@"Content-Type"];<br>
> > > [request setValue:postBodyLength forHTTPHeaderField:@"C=
ontent-<br>
> > > Length"];<br>
> > > [request setHTTPBody:[postBody<br>
> > > dataUsingEncoding:NSUTF8StringEncoding]];<br>
><br>
> > > This type of formatting works just fine for my xAuth authent=
ication.<br>
><br>
> > > On Jun 15, 4:44 pm, themattharris <<a href=3D"mailto:them=
atthar...@twitter.com">thematthar...@twitter.com</a>> wrote:<br>
> > > > Hey Craig,<br>
><br>
> > > > Could you let us see what the authorization header you =
are sending<br>
> > > > looks like (obfuscating your oauth keys and secrets)?<b=
r>
><br>
> > > > What you're aiming for is a header similar to this:=
<br>
><br>
> > > > POST /1/statuses/update.xml HTTP/1.1<br>
> > > > Accept: */*<br>
> > > > Connection: close<br>
> > > > User-Agent: OAuth gem v0.4.0<br>
> > > > Content-Type: application/x-www-form-urlencoded<br>
> > > > Authorization: OAuth<br>
> > > > =C2=A0 oauth_consumer_key=3D\"xxxxxxxxxxxxxxxxxxxx=
xxxx\",<br>
> > > > =C2=A0 oauth_nonce=3D\"xxxxxxxxxxxxxxxxxxxxxxxxxxx=
x\",<br>
> > > > =C2=A0 oauth_signature=3D\"xxxxxxxxxxxxxxxxxxxxxxx=
x\",<br>
> > > > =C2=A0 oauth_signature_method=3D\"HMAC-SHA1\"=
,<br>
> > > > =C2=A0 oauth_timestamp=3D\"1276634179\",<br>
> > > > =C2=A0 oauth_token=3D\"xxxxxxxxxxxxxxxxxxxxxxxxxxx=
xxx\",<br>
> > > > =C2=A0 oauth_version=3D\"1.0\"<br>
> > > > Content-Length: 27<br>
> > > > Host: <a href=3D"http://api.twitter.com" target=3D"_bla=
nk">api.twitter.com</a><br>
><br>
> > > > With your post body being the status you are sending. S=
imilar to:<br>
><br>
> > > > status=3Dsomething%20to%20say<br>
><br>
> > > > Matt<br>
><br>
> > > > On Jun 13, 8:32 pm, Craig <<a href=3D"mailto:chanson=
9...@gmail.com">chanson9...@gmail.com</a>> wrote:<br>
><br>
> > > > > Ok, so I believe my signature is correct because i=
f I take out the<br>
> > > > > oauth_token parameter from the signature base I ge=
t an incorrect<br>
> > > > > signature error instead of the invalid/used nonce =
error. =C2=A0I am<br>
> > > > > definitely posting to the correct url: "<a hr=
ef=3D"https://api.twitter.com/1/" target=3D"_blank">https://api.twitter.com=
/1/</a><br>
> > > > > statuses/update.xml" because if I change it I=
get an invalid url<br>
> > > > > response. =C2=A0The nonce I'm generating is un=
ique for every request I'm<br>
> > > > > sending. =C2=A0The timestamp is accurate to the nu=
mber of seconds that have<br>
> > > > > passed since unix epoch. =C2=A0Obviously the inval=
id/used nonce error is<br>
> > > > > garbage.<br>
><br>
> > > > > Here's the formatting of my URL request in obj=
c:<br>
><br>
> > > > > // Create the request<br>
> > > > > NSString* requestString=3D [NSString<br>
> > > > > stringWithFormat:@"%@",TWITTER_STATUS_UP=
DATE_URL];<br>
> > > > > NSMutableURLRequest* request =3D [[NSMutableURLReq=
uest alloc]<br>
> > > > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 initWithURL:=
[NSURL<br>
> > > URLWithString:requestString]<br>
><br>
> > > cachePolicy:NSURLRequestReloadIgnoringCacheData<br>
> > > > > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 timeoutInterval:30.0];<br>
> > > > > [request setHTTPMethod:@"POST"];<br>
> > > > > [request addValue:authHeader forHTTPHeaderField:@&=
quot;Authorization"];<br>
> > > > > [request setValue:@"application/x-www-form-ur=
lencoded"<br>
> > > > > forHTTPHeaderField:@"Content-Type"];<br>
> > > > > [request setValue:postBodyLength forHTTPHeaderFiel=
d:@"Content-<br>
> > > > > Length"];<br>
> > > > > [request setHTTPBody:[postBody<br>
> > > > > dataUsingEncoding:NSUTF8StringEncoding]];<br>
><br>
> > > > > Any other ideas? =C2=A0I'm at a total loss as =
to why this might be<br>
> > > > > happening.<br>
><br>
> > > > > Thanks,<br>
> > > > > Craig<br>
><br>
> > > > > On Jun 13, 3:42 pm, Craig <<a href=3D"mailto:ch=
anson9...@gmail.com">chanson9...@gmail.com</a>> wrote:<br>
><br>
> > > > > > No dice. =C2=A0I just tried creating a new ap=
p and using the new<br>
> > > keys/token<br>
> > > > > > to tweet. =C2=A0I'll go over my steps onc=
e more and see if I can track<br>
> > > down<br>
> > > > > > an issue somewhere...<br>
><br>
> > > > > > On Jun 11, 8:53 pm, Taylor Singletary <<a =
href=3D"mailto:taylorsinglet...@twitter.com">taylorsinglet...@twitter.com</=
a>><br>
> > > > > > wrote:<br>
><br>
> > > > > > > xAuth in this case, I think, is unrelate=
d to the issue. If you can<br>
> > > use<br>
> > > > > > > a different key and use the "my tok=
en" feature to get your access<br>
> > > > > > > token, then try to tweet using that toke=
n, it will sufficiently<br>
> > > > > > > express the problem I think.<br>
><br>
> > > > > > > Taylor<br>
><br>
> > > > > > > On Jun 11, 2010, at 2:48 PM, Craig <<=
a href=3D"mailto:chanson9...@gmail.com">chanson9...@gmail.com</a>> wrote=
:<br>
><br>
> > > > > > > > Hello,<br>
><br>
> > > > > > > > I have an iphone app that is using =
xauth. =C2=A0I am able to obtain<br>
> > > the<br>
> > > > > > > > access token with no problem at all=
. =C2=A0When I go to post a status<br>
> > > > > > > > update, I receive an invalid / used=
nonce error. =C2=A0It can't<br>
> > > actually be<br>
> > > > > > > > a used nonce since I have checked t=
his multiple times. =C2=A0Here are<br>
> > > the<br>
> > > > > > > > details of the post:<br>
><br>
> > > > > > > > url:<br>
> > > > > > > ><a href=3D"http://api.twitter.com/1/=
statuses/update.xml" target=3D"_blank">http://api.twitter.com/1/statuses/up=
date.xml</a><br>
><br>
> > > > > > > > signature base string:<br>
> > > > > > > > POST&http%3A%2F%<a href=3D"http=
://2Fapi.twitter.com" target=3D"_blank">2Fapi.twitter.com</a>%2F1%2Fstatuse=
s<br>
> > > > > > > > %2Fupdate.xml&oauth_consumer_ke=
y%3Dmyconsumerkey%26oauth_nonce<br>
> > > > > > > > %3D397vi5Ug1YHC3UAVUAoB%26oauth_sig=
nature_method%3DHMAC-<br>
> > > > > > > > SHA1%26oauth_timestamp%3D1276292596=
%26oauth_token%3Dmytoken<br>
> > > > > > > > %26oauth_version%3D1.0%26status%3Dm=
y%2520tweet<br>
><br>
> > > > > > > > Authorization header:<br>
> > > > > > > > OAuth oauth_nonce=3D"397vi5Ug1=
YHC3UAVUAoB",<br>
> > > oauth_signature_method=3D"HMAC-<br>
> > > > > > > > SHA1", oauth_timestamp=3D"=
;1276292596",<br>
> > > > > > > > oauth_consumer_key=3D"myconsum=
erkey", oauth_token=3D"mytoken",<br>
> > > > > > > > oauth_signature=3D"yOh2zQPGDBl=
VEP5cDWhjddQWTLc%3D",<br>
> > > oauth_version=3D"1.0"<br>
><br>
> > > > > > > > Content-Type:<br>
> > > > > > > > [request setValue:@"applicatio=
n/x-www-form-urlencoded"<br>
> > > > > > > > forHTTPHeaderField:@"Content-T=
ype"];<br>
><br>
> > > > > > > > I can see no reason why this should=
n't work. =C2=A0Any help would be<br>
> > > > > > > > greatly appreciated!<br>
><br>
> > > > > > > > Thanks,<br>
> > > > > > > > Craig<br>
</div></div></blockquote></div><br></div>
--00c09f905ff3da547a04892b112e--
Message from discussion oauth status update returning error 401 invalid / used nonce
| Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy |
| ©2013 Google |