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
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
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
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
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
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
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
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
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
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
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
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 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
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
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
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
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
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
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
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
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
Hi Berto,
I can confirm that using POST operations over HTTPs will work for XAuth.
Your URL should only contain: https://api.twitter.com/oauth/access_token
Your signature base string should contain the x_auth_* parameters.
Your authorization string should not contain the x_auth_* parameters.
In case if anyone's interested (though I doubt there are many
Erlang'ers on the list),
I just added xAuth support to twerl.
http://github.com/ak1394/twerl
Regards,
Anton
On Wed, Mar 3, 2010 at 4:57 PM, Berto mstbe...@gmail.com wrote:
Raffi,
Can you comment on the first part of Marc's last
* Berto mstbe...@gmail.com [100303 06:42]:
Isn't that using a GET request versus the docs saying POST? And I
thought parameters were supposed to be normalized except for signature
which gets attached at the end?
Hmmm. I completely missed the fact that the documentation specifies
POST. I used
Try passing in nil as the token. The access token request should be similar to
how you used to perform the request token request.
The best explanation (and they one that helped me) is from Steve Reynolds:
http://ke-we.net/7u
isaiah
http://twitter.com/isaiah
On Mar 1, 2010, at 1:26 PM,
* Berto mstbe...@gmail.com [100302 13:28]:
At first I thought this might be because HttpURLConnection wasn't
handling SSL, but then I switched over to HttpPost (this code is in
Java) which I know will handle SSL and I'm still getting a 401. I'm
doing everything the same as with oauth, except
38 matches
Mail list logo
