Was the cause of the empty response body ever discovered? I'm having
a similar issue, except my 401 response body has Content-Length: 1
containing an empty space .
On Nov 19 2010, 3:44 pm, Matt Harris thematthar...@twitter.com
wrote:
Hey Chrys,
Agreed. The authentication header doesn't have
cool thanks ;)
I just wrote you back with all the details
Iman
On 15 déc, 19:51, Brian Sutorius bsutor...@twitter.com wrote:
We attempt to respond to these requests within a couple business days.
I just located your ticket and will follow up now.
Brian Sutorius
On Dec 15, 4:53 am, Iman
Your xAuth is not approved and activated yet - 401 error
On Dec 12, 6:59 pm, Mchello mchel...@gmail.com wrote:
I use this source athttps://github.com/aral/XAuthTwitterEngine
first..
I register my App at dev.twitter.com
and send message to a...@twitter.com .. about Xauth Key..
and i get
HI Tom
Thank you very much for Your kind Support.Still i could not able to get
Response from Twitter from firefox and samsung TV app.
But it is working in Safari.Here i am sending the clean code as an
attachment please help me out where the hurdle exist.
If you make it work in firefox surely
That code is really a mess, but I think I found a few issues and solved
them. I'm not sure about the Signature itself, but the Base String is
fine now.
I've attached a new version of your .html file. I won't paste the code
here because it may break the code.
Tom
PS: I really recommend
I am interested in solving this too.
Let's say Samsung TV is same as desk top. You should be able to use
xAuth.
You need to create a new Twitter app to get Consumer key and Consumer
secret. Make sure you select client method and read/write.
On Dec 6, 1:23 am, umamahesh G.
HI Tom,
Thanks for you kind support.I had all required privileges from twitter for
my app.The thing is i can able to post the message from safari but same
code not working in firefox,IE as well as samsung Tv.Please help me out from
this problem.I tried maximum ways still i don't have any
Hey Chrys,
The order of the parameters in the base string matter and they should be in
lexicollexicographical order. For ease of debugging and to remove any
ambiguity it would be better to have the authorization header use the same
order too.
Can you tell me what the body content of the 401
Twitter 401 error is related to Authentication
401 Unauthorized: Authentication credentials were missing or
incorrect.
Another debugging is to print out error type error message from iPhone
console
On Nov 19, 11:04 am, Matt Harris thematthar...@twitter.com wrote:
Hey Chrys,
The order of the
Hey Matt,
I am using Loren Brichter's OAuthCore library to create the
Authorization header... so I imagine he did it correctly.
The body content of the 401 is empty. Content-Length: 0
On Nov 19, 11:04 am, Matt Harris thematthar...@twitter.com wrote:
Hey Chrys,
The order of the parameters in
Yeah, I've done that. Authentication credentials meaning my oAuth
credentials, or xAuth credentials?
On Nov 19, 11:41 am, Bess bess...@gmail.com wrote:
Twitter 401 error is related to Authentication
401 Unauthorized: Authentication credentials were missing or
incorrect.
Another debugging is
Also, the example here shows that the Auth header and the base string
aren't in the same order:
http://dev.twitter.com/pages/xauth
On Nov 19, 11:04 am, Matt Harris thematthar...@twitter.com wrote:
Hey Chrys,
The order of the parameters in the base string matter and they should be in
Hey Chrys,
Agreed. The authentication header doesn't have to be in order but as said
previously, it helps with debugging.
It is really strange that the response body is empty. It maybe easier if you
email me the full request headers, with response headers and content so I
can debug further. For
*bump*
I've run my base string through an oAuth verifier (http://quonos.nl/
oauthTester/), and it all checks out!
Any ideas?
On Oct 27, 4:50 pm, Chrys Bader chr...@gmail.com wrote:
Hey all,
This is my first post in this group, hi!
I am having trouble making a request
Hey Chrys,
A couple of things to check first:
1. Have you been granted xAuth access?
2. Double check the timestamp of your request is within 10 or so
minutes of the time returned by Twitter's servers. Our server time is
in UTC.
3. Verify your encoding is correct. For example: a password like ab$
1. Yes
2. Interesting point. I'm probably not sending a UTC timestamp!
3. We take care of this
Thanks! I'm going to play with the timstamp.
On Nov 18, 5:53 pm, themattharris thematthar...@twitter.com wrote:
Hey Chrys,
A couple of things to check first:
1. Have you been granted xAuth access?
Ok, I looked into it. According to the iPhone SDK documentation, I am
indeed sending the UTC (GMT) timestamp.
Still not sure what else could be wrong?
Is this the right Content-Type?
Content-Type = application/x-www-form-urlencoded; charset=utf-8;
On Nov 18, 5:53 pm, themattharris
OK, but is the UTC timestamp actually accurate? we've heard of a number of
phones whose date/time are wildly wrong. It maybe find but it's quite
common.
Your content-type is fine.
Matt
On Thu, Nov 18, 2010 at 6:03 PM, Chrys Bader chr...@gmail.com wrote:
Ok, I looked into it. According to the
Yes I compared the UTC timestamp that my phone is generating with the
actual UTC timestamp, and they were the same.
Is there anything else I can show you for more information?
No matter what, I just keep getting a 401 response from Twitter.
On Nov 18, 6:41 pm, Matt Harris
Does the order of the params in either the Authorization or Base
string matter?
Here are my Request Headers:
Authorization = OAuth oauth_timestamp=\1290134876\, oauth_nonce=
\D3EC42D2-A37F-4298-987D-0F9603B0C9C7\, oauth_version=\1.0\,
oauth_consumer_key=\xxx\,
Hi,
My App working fine on other language machine but in chinese machine I
use same code for singnatrue generation, and request look like same
but in response I got 401 error.
Thanks,
Pawan Singh
On Nov 4, 1:49 pm, engine.start 477914...@163.com wrote:
Have you test your singnatrue by the
Hi,
Thanx for reply but still in reply I got same problem (The remote
server returned an error: (401) Unauthorized.). I add this line in my
web request webRequest.Headers.Add(Accept-Language: zh-CN,en,*);
But no sucess.
:(
On Nov 3, 11:03 am, engine.start 477914...@163.com wrote:
Hi,
Your
Have you test your singnatrue by the way http://quonos.nl/oauthTester support ?
(not only the base)
And have you captured your request ? Maybe youshould do this job first, and
then again on a non-chinesemachine,
you will get the answer.
At 2010-11-04 16:20:05，pawan
Hi,
Your problem maybe same as mine.
chang url to another website, do not use ssl, wireshark your request, and then
compare with this, maybe it will work.
(I use libcurl, and add User-Agent: Mozilla/5.0 to httpheader, and it work)
POST
Thanks for reply but after using this http://quonos.nl/oauthTester URL
I got my base string is ok and still I not able to find out how to
resolve this issue.
On Nov 2, 12:32 am, Tom van der Woerdt i...@tvdw.eu wrote:
Hi,
Most 401 Unauthorized errors (and especially the ones involving UTF8
The credentials are the same. It will only generate a new nonce and
timestamp.
On 5 Okt., 19:05, Taylor Singletary taylorsinglet...@twitter.com
wrote:
It's likely not the nonce that is invalid in this case -- or the timestamp.
In this case, the error specifically is indicating that it
The credentials are the same. It will only generate a new nonce and
timestamp.
On 5 Okt., 19:05, Taylor Singletary taylorsinglet...@twitter.com
wrote:
It's likely not the nonce that is invalid in this case -- or the timestamp.
In this case, the error specifically is indicating that it
Hello again,
I still have problems that I sometimes get a successful response, and
a couple of times a faulty response.
If I get a bad response, then four hundred and first with the status
code The error message uist following:
Failed to validate oauth signature and token
The values that are
On 27 Sep., 11:41, Tom van der Woerdt i...@tvdw.eu wrote:
401 is a general HTTP error code. The message is more important.
If the message is about an invalid nonce, then you should check the
timestamp. If it's about a nonce that had already been used, check the
nonce. If it's a signature
On 27 Sep., 11:41, Tom van der Woerdt i...@tvdw.eu wrote:
401 is a general HTTP error code. The message is more important.
If the message is about an invalid nonce, then you should check the
timestamp. If it's about a nonce that had already been used, check the
nonce. If it's a signature
Hello again,
I still have problems that I sometimes get a successful response, and
a couple of times a faulty response.
If I get a bad response, then four hundred and first with the status
code The error message uist following:
Failed to validate oauth signature and token
The values that are
Hello again,
I still have problems that I sometimes get a successful response, and
a couple of times a faulty response.
If I get a bad response, then four hundred and first with the status
code The error message uist following:
Failed to validate oauth signature and token
The values that are
Hi Doug,
The only thing I can think of is that you aren't sending an
Authorization: header that starts with OAuth.
Tom
On Sep 26, 10:30 pm, Doug doug_d...@yahoo.com wrote:
Hi folks,
I have been banging my head against the wall trying to figure out why
I keep getting 'failed to validate
In the last post from
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/51f25b873868e920/9babee82d344f7ee?lnk=gstq=failed+to+validate+oauth+signature+and+token#9babee82d344f7ee
there is code which works for me. Maybe it'll help
On Sep 26, 10:30 pm, Doug
LOL thanks that was it (palm-to-face).
Thanks for the suggestions folks
On Sep 27, 3:38 am, Tom van der Woerdt i...@tvdw.eu wrote:
Hi Doug,
The only thing I can think of is that you aren't sending an
Authorization: header that starts with OAuth.
Tom
On Sep 26, 10:30 pm, Doug
I don't know what's going on and need more information to be able to tell
you. What's the name of the Twitter account that you have used to register
your application?
Taylor
On Wed, Sep 22, 2010 at 8:35 PM, privatejava ngmm...@gmail.com wrote:
I 'm suprised..today when I came to compile my all
I 'm suprised..today when I came to compile my all classfile and
changed my library of twitter api to new version.
Also as you said i changed date first to Jan 01 2010 and again at Sept
22 the xAuth worked fine without any exception.
Can you tell me what is happening on me.. I don't know how it
Thank you. Now it works.
So what is needed was a single HTTP header with name Authorization
and value is the comma delimited string with quoted values as shown in
the example.
In other words...
POST /oauth/authorize HTTP/1.1
Authorization: OAuth
What algorithm you're using for hmac-sha1 and base64
I'm getting different oauth_signature for the xAuth test example
http://dev.twitter.com/pages/xauth
Nikolay Klimchuk
On Sep 13, 1:01 am, Double K squel...@gmail.com wrote:
hi, my name is Kim.
I will make XAuth module. So i need developer
I have been trying to get the time synchronized with the twitter
server but could not attain it so far. Can anyone help me with code.
It'll be real help as I have already wasted 3 days for this task.
Warm Regards,
On Sep 2, 6:11 am, MigrantP migra...@gmail.com wrote:
Scratch that, it was simply
@Tom, your OAuth validator is the best thing I've ever seen, it helped
me solve the problem in a couple of minutes...
@Taylor, you are right, I was encoding way more than I should have
been, fixed it!
Thanks both!
Garry
On Sep 6, 4:22 pm, Tom van der Woerdt i...@tvdw.eu wrote:
You should try
You shouldn't synchronize to Twitter. You (and Twitter) should
synchronize to the World Time Standard using NTP. It's a simple
process on Linux - you just install a package or two and read your
distro's system administration manual on how to configure it. It's
point and click on openSUSE
Yeah, well, that doesn't work very well for desktop apps ;-) Users would
go mad if you suddenly change their clocks.
Tom
On 9/6/10 10:22 PM, M. Edward (Ed) Borasky wrote:
You shouldn't synchronize to Twitter. You (and Twitter) should
synchronize to the World Time Standard using NTP. It's a
Users of my xAuth application are also getting 401, since about 12
hours ago.
Steve
--
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
Dear Taylor,
I am developing an twitter app in MTK (Mediatek platform and my app
has the x-auth privilages)
My Issue:
I am getting errocode 401 (Failed to validate oauth signature and
token), only in the mobile (MTK - media tek - where I am not using
proxy).
I ma getting the x-auth access
We have fixed a bug in our OAuth implementation that allowed timestamps in
the future to be accepted. We've now corrected this such that timetsamps
must be within a reasonable amount of time in cosideration to Twitter's
server clocks.
We return our current time in the Date HTTP header of every
You should sort the fields in the Base String.
Tom
On 9/1/10 6:35 PM, Karthik wrote:
Dear Taylor,
I am developing an twitter app in MTK (Mediatek platform and my app
has the x-auth privilages)
My Issue:
I am getting errocode 401 (Failed to validate oauth signature and
token), only in
Dear Tom,
its is in sorted order only. And moreover the same order working fine
in Simualtor
On Sep 1, 9:37 pm, Tom van der Woerdt i...@tvdw.eu wrote:
You should sort the fields in the Base String.
Tom
On 9/1/10 6:35 PM, Karthik wrote:
Dear Taylor,
I am developing an twitter app in
For desktop apps using oAuth, the timestamp issue causing 401 errors
is a big problem. People's desktops have all sorts of crazy times set
on them. This means now every application that uses Twitter oAuth
needs to have code written to sync/modify its time with Twitter's.
It's a pain.
--
Twitter
This is true of all applications running to spec. We've always denied
requests that were behind our system clock by an unreasonable amont -- you
would be presented with this conundrum in that scenario as well, regardless
of our recent change to also apply this restriction to timestamps in the
Sure. I implemented it and it was not hard, just one more thing to
deal with, that's all. :)
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker:
Thanks - the problem was that the library routine I used for the Unix
timestamp didn't take Daylight Savings into account!
Steve
On Sep 1, 5:35 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
We have fixed a bug in our OAuth implementation that allowed timestamps in
the future to be
i'm on my way to fix this, but i wonder why you didn't let us know
about this change ???
On Sep 1, 8:44 pm, Steve Loft kettletoft@googlemail.com wrote:
Thanks - the problem was that the library routine I used for the Unix
timestamp didn't take Daylight Savings into account!
Steve
On Sep
Oh, sorry, you are right. You replaced the consumer key with some random
value but apparently you also replaced the 3D in %3D so my validator
didn't catch it properly.
Tom
On 9/1/10 6:42 PM, Karthik wrote:
Dear Tom,
its is in sorted order only. And moreover the same order working fine
in
Sorry for the trouble our alignment has caused.
Honestly, we should have announced we were going to harden this, but -- and
really we should have learned our lesson on this -- we were operating under
the assumption that OAuth clients develop to spec, which includes presenting
the current epoch
Peoples' desktops are almost all Windows (90%) or MacOS X (9%). I
don't know about Macs but I know for a fact that Windows XP and later
desktops can be *easily* syncronized to world time via NTP - in
fact, Microsoft has servers!
And for the 1% outliers like me (openSUSE 11.3) there are
I should mention that I am having no problem posting updates to
twitter itself, but I cannot post pictures through twitpic or yfrog
due to this error.. and it was working earlier with no code change
since.
On Sep 1, 5:02 pm, MigrantP migra...@gmail.com wrote:
I am also getting this problem,
Scratch that, it was simply a bonehead error on my part.. carry on =)
On Sep 1, 5:25 pm, MigrantP migra...@gmail.com wrote:
I should mention that I am having no problem posting updates to
twitter itself, but I cannot post pictures through twitpic or yfrog
due to this error.. and it was working
If my memory serves it took them about a week to authorize us for
xAuth. It's a by-hand process and my impression is that the function
is understaffed.
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
I got the same problem.
On Jul 23, 4:19 pm, DrewC drew.cogb...@smallplanet.com wrote:
I'm getting a 401 when I try to usexAuthin my iPhone app. Is this
occurring for others?
Hi folks,
Sorry to hear you're having trouble getting xAuth to work.
First question: Have you applied for and been approved for xAuth privileges?
Second question: If so, was this previously functioning for you and only now
not working?
Third question: Can you share, without compromising your
As far as we know this is resolved and things should be working fine.
I'm not familiar with your setup so need to ask if you applied for xAuth and
were granted it?
If not that will be the causes of the 401. If you did what API call are you
trying to make and what does your signature base string
Isaiah,
I seem to be getting similar errors with regular OAuth requests. If
I'm already logged into twitter and OAuth just needs to redirect, it
works, but if I land on the login page, enter my username and password
and click submit, the redirect breaks with the 500 error.
Ashish
On Jul 19,
Im getting the same isalah. Twitter are aware of the issue. its during
handshake for creating new tokens and maybe linked to several other
OAuth issues that came to attention this morning.
Im hoping it will be fixed shortly!
OK, good to know. Just want to make sure it's not just me. Misery loves
company, I guess. :-P
isaiah
http://twitter.com/isaiah
On Jul 19, 2010, at 2:54 PM, Tim Davies wrote:
Im getting the same isalah. Twitter are aware of the issue. its during
handshake for creating new tokens and maybe
Hi Taylor,
Finally some reason to smile. I got it working! Earlier i tried with
the time stamp as seconds..but that too didnt work.
The issue was to do with Body of the request. I was url encoding the
entire string.
x_auth_mode%3Dclient_auth%26x_auth_password%3DPASSWORD
right I've got passed this error (x_auth_Mode needed a lower case m)
but now get Failed to validate oauth signature and token.
My signature looks looks this, I'm pretty sure this should be working
as worked with the test case example off the documentation
Hi Taylor,
Thanks for the prompt reply
consumer key = vfM8qYNAEBfZsofKDNX65Q
consumer secret = fwBTEa4GRCPkszO26ma5mFLi1aInV82JTxJWbuL26g
token key = 13073932-seUruGITdpHxCJsoUhpjectP4hpdRubW62Q7nftyA
token secret = Y0cXVWuoymSiVRRhFMpCoHqQuJ2BxNSjRqotpRZx0
thanks
-chiu
On Jun 16, 12:35 pm,
Hi Chiu,
You're going to want to reset your keys on your application settings on
dev.twitter.com -- we will really recommend not posting your consumer
secrets to the group -- but easy to rectify if you go and change your keys.
Your signature base string is actually a bit different than your
favorites/create should be a POST. Try:
$response = $connection-post( 'favorites/create', array ('id' = $status_id
) );
Abraham
-
Abraham Williams | Hacker Advocate | http://abrah.am
@abraham | http://projects.abrah.am | http://blog.abrah.am
This email is: [ ] shareable [x] ask first
If I do a HTTP POST - i got error message saying that
This method requires a GET.
On Jun 16, 1:00 pm, Abraham Williams 4bra...@gmail.com wrote:
favorites/create should be a POST. Try:
$response = $connection-post( 'favorites/create', array ('id' = $status_id
) );
Abraham
-
The signature base string is the following
zZyk1NxKlpXZEapSszao6PCIAQM=
$signature = $this-build_signature($signature_method, $consumer,
$token);
thanks
-chiu
On Jun 16, 12:57 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi Chiu,
You're going to want to reset your keys on your
Request =
/1/favorites/create.json?
id=16170711730oauth_consumer_key=vfM8qYNAEBfZsofKDNX65Qoauth_nonce=6c2b0e1a7af3dd0b60680c8860e63454oauth_signature=zZyk1NxKlpXZEapSszao6PCIAQM
%3Doauth_signature_method=HMAC-
SHA1oauth_timestamp=1276724507oauth_token=13073932-
Let us continue this on the issue tracker so we don't spam the list as
much: http://github.com/abraham/twitteroauth/issues#issue/33
Abraham
-
Abraham Williams | Hacker Advocate | http://abrah.am
@abraham | http://projects.abrah.am | http://blog.abrah.am
This email is: [ ] shareable
The URL to create a favorite using the API is a POST to:
/1/favorites/create/id.format
So in your case it would be:
/1/favorites/create/16170711730.json
Give that a try and let us know how it goes. I know the docs on
dev.twitter.com are incorrect for this so i'll be updating them soon.
On
Yes, you are right,
abraham mention that the following will fix the problem
$response = $connection-post('favorites/create/' . $status_id);
-chiu
On Jun 16, 2:51 pm, Matt Harris thematthar...@twitter.com wrote:
The URL to create a favorite using the API is a POST to:
Thanks Jann, let us know how it goes now that you have an official
ticket...
Abraham, is it usually a couple days from when the email is received
or from the successful creation of a ticket?
Jeff
On Jun 1, 12:01 pm, Abraham Williams 4bra...@gmail.com wrote:
Processing for XAuth is usually
On Tue, Jun 1, 2010 at 10:06, jsleuth jsle...@gmail.com wrote:
Abraham, is it usually a couple days from when the email is received
or from the successful creation of a ticket?
They should both happen within minutes of each other so my answer is yes.
Abraham
--
Abraham Williams | Developer
Well played. :-) However, I fear the issue I'm facing is that no
service ticket is being created when I submit my request-- the
twitter ticket system says that I do not have access to request my
ticket (and that it 'may' have been deleted). Is a ticket
automatically created when I send an
Really good question!
Maybe there should be a diff way to request access, like a separate category in
the why are you contacting us drop-down on the support ticketing system.
Just a thought.
J
On Jun 1, 2010, at 12:55 PM, jsleuth wrote:
Well played. :-) However, I fear the issue I'm
Yeah, Jann, exactly. Something along those lines would be great. At
least I wouldn't be flooding their inbox with redundant requests out
of concern that my request went into a black hole...
JS
On Jun 1, 4:00 pm, Jann Gobble janngob...@gmail.com wrote:
Really good question!
Maybe there
Hey Everyone!
We know there are some issues with tickets right now -- they aren't being
lost, but the conversion to our new version of the help center has not been
without some hiccups. We have a very large backlog of xAuth requests right
now and only very few resources available to process the
Taylor,
I only see the second one.
The first: 1008949 is lost in the ether. Again, here is the issue: We email a
request to api@ from whatever email address.. A support request confirmation
comes back to us with a link that forces us to log in. When we log in, ticket
searches are limited
Thanks for the feedback Taylor.
None of the ticket numbers for my submissions appear on that page
(#1007543, #1009988, #1013602).
To clarify what we should expect: Our email requests for xAuth
permissions have generated tickets (even if we can't see or access
them) that will be responded to as
I'll see what I can do about getting the other ticket assigned correctly --
As a general rule/advice, always send your support requests to
a...@twitter.com from the email address of the account associated with the
applications you are trying to whitelist -- for this reason, among others
(it makes
On Tue, 1 Jun 2010 13:08:12 -0700
Taylor Singletary taylorsinglet...@twitter.com wrote:
Hey Everyone!
We know there are some issues with tickets right now -- they aren't
being lost, but the conversion to our new version of the help center
has not been without some hiccups. We have a very
Same here. I get this with the XAuthTwitterEngineDemo:
Twitter request failed: BCC3F69C-36CE-4C86-B50B-8E8B094E2DCD with
error:Error Domain=HTTP Code=403 Operation could not be completed.
(HTTP error 403.)
Has any of you guys figured out how to fix this?
On Apr 26, 7:00 pm, luckyman
Item closed. Twitter now returns 403 when re-sending the same message,
which is what the referenced demo program does.
On May 15, 12:56 pm, neptune2000 papa.ma...@gmail.com wrote:
I have been using the xAuth code by Aral Balkan for my iPhone apps:
http://aralbalkan.com/3133/
The code had
Ok, this is what I have.
- I am using HTTP headers
- I am using POST.
- Regarding SSL, does that mean I have to use https instead of http?
If that's so, then I am doing it. I'm unaware if there's something
else.
- I'm unsure of what you mean by this and the next point. This is my
HTTPBody:
Great Fernando, I'm glad you got it figured it out!
Taylor Singletary
Developer Advocate, Twitter
http://twitter.com/episod
On Thu, Apr 29, 2010 at 9:26 PM, Fernando Olivares aeris@gmail.comwrote:
Got it.
The signatureBaseString has to include the parameters, so after the
oauth version
Well I don't like that.. does anybody here think about user
experience? What is a rock solid security model good for, when nobody
uses it because it's just cumbersome? As always in life, trade offs
need to be made. I could design a black box where nothing would ever
get in or out, but this box
On Thu, Apr 29, 2010 at 03:17, Ivo ivo.wet...@googlemail.com wrote:
Also I can't find the word Browser in Twitter Client, and what's
so secure about the Browser anyway? There's no reason to trust it!
It's just another program, like the Twitter Client of your choice is
too. Or can you make
I think I never sent my answer. If I did, please ignore this or I'll
delete it myself.
Anyway, here's a summary of what I'm doing.
- I am using HTTP headers and POST.
- I am a bit confused about SSL. If all I have to do to use SSL is use
https instead of http, then I'm good.
Here's my post
Also, here's my signature string:
POSThttps%3A%2F%2Fapi.twitter.com%2Foauth
%2Faccess_tokenoauth_consumer_key%3DjbEiZQ85zjOamkhVRTclnA
%26oauth_nonce%3DE23ADF41-F137-4E33-
BC51-00AEB7C95439%26oauth_signature_method%3DHMAC-
SHA1%26oauth_timestamp%3D1272598628%26oauth_version%3D1.0
Here's how it
Got it.
The signatureBaseString has to include the parameters, so after the
oauth version I was missing the x_auth_mode and the other 2
parameters.
Thanks for your help!
Thanks for the info Raffi. I'll give it another day or two before
following up on the status.
On Apr 26, 3:29 pm, Raffi Krikorian ra...@twitter.com wrote:
it should be on the order of days (hopefully less - depends on our backlog
and our queue).
On Mon, Apr 26, 2010 at 11:52 AM, Tony
I have same error.
Error: Error Domain=NSURLErrorDomain Code=-1012 UserInfo=0x42969d0
Operation could not be completed. (NSURLErrorDomain error -1012.)
I will using XAuthTwitterEngineDemo
I have approval But error may be source error..
Twitter Support Mail
Thank you for your interest in xAuth.
Hi,
I have same problem.
Received approval from Twitter.
But the same thing.
Do you have solutions?
On Apr 21, 5:13 am, sae twitp...@gmail.com wrote:
Hi,
I just set up my application forxauthand started testing.
It keeps failing with error message:
Error Domain=NSURLErrorDomain
Yes, a...@twitter.com granted my app for xAuth...
Any suggestion on what I should do to fix the issue?
I did all I can and I'm STUCK at the point.
This xauth issue is holding back the release of my app for a week :(
-Sae
On Apr 20, 1:27 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Yes, a...@twitter.com granted my app for xAuth...
Any suggestion on what I should do to fix the issue?
I did all I can and I'm STUCK at the point.
A little easy googling (for NSURLErrorDomain error 1012) turned up
1 - 100 of 116 matches
Mail list logo
