This likely wasn't due to adding the source parameter. It was more
likely but due to a bug I had in the streaming OAuth implementation.
Java's URLEncoder converts spaes to '+' instead of '%20'. This got
fixed yesterday.
---Mark
http://twitter.com/mccv
On Mon, Jun 28, 2010 at 5:08 PM,
Wil: Can you retrieve the signature base string (again, from your current
work) from your library when attempting the call that returns 401? There
must be something minor going amiss there with this parameter for some
reason.
Thanks,
Taylor
On Sat, Jun 26, 2010 at 12:08 PM, John Kalucki
Hi Taylor,
Ok. Here's the entire thing:
Generated base string:
POSThttp%3A%2F%2Fstream.twitter.com%2F1%2Fstatuses
%2Ffilter.jsonfollow%3D156934710%26oauth_consumer_key
%3DrHYIlqotmSfiGc6OfFtw%26oauth_nonce
%3Dmvzi5szav5dciif4%26oauth_signature_method%3DHMAC-
Ah wait, I ran a couple more tests just to be sure and the signatures
match the sent sniffed one guess I missed something previously...
Base:
POSThttp%3A%2F%2Fstream.twitter.com%2F1%2Fstatuses
%2Ffilter.jsonfollow%3D156934710%26oauth_consumer_key
The thing wasn't including the POST parameters in the signing! I think
I got it!
On Jun 28, 10:54 pm, Wil willi...@gmail.com wrote:
Ah wait, I ran a couple more tests just to be sure and the signatures
match the sent sniffed one guess I missed something previously...
Base:
Great! Let me know if you still need assistance.
Taylor
On Mon, Jun 28, 2010 at 8:10 AM, Wil willi...@gmail.com wrote:
The thing wasn't including the POST parameters in the signing! I think
I got it!
On Jun 28, 10:54 pm, Wil willi...@gmail.com wrote:
Ah wait, I ran a couple more tests
Oh wait, it does include them I just missed it.
So much for premature celebration...
On Jun 28, 11:10 pm, Wil willi...@gmail.com wrote:
The thing wasn't including the POST parameters in the signing! I think
I got it!
On Jun 28, 10:54 pm, Wil willi...@gmail.com wrote:
Ah wait, I ran a
Let's start from a common point. By using the same inputs, we can try and
meet in the middle with exactly the same signature, signature base string,
and authorization header.
Using the following values:
Consumer Key: TwitterConsumerKey
Consumer Secret: TwitterConsumerSecret
Access Token:
Hi,
I got exactly the same values:
Base string:
POSThttp%3A%2F%2Fstream.twitter.com%2F1%2Fstatuses
%2Ffilter.jsonfollow%3D156934710%26oauth_consumer_key
%3DTwitterConsumerKey%26oauth_nonce%3Dabcdefgh%26oauth_signature_method
%3DHMAC-SHA1%26oauth_timestamp%3D1277739588%26oauth_token
Hi again,
I made a real request this time because in the previous one, I
couldn't control the nonce and timestamp generation directly so I copy-
pasted the code it used and modified it a bit. This is the real
generated data which has a non-mock nonce and timestamp.
Timestamp: 1277742686
Nonce:
Hi Wil,
Did some more tests. Why are you passing source in this context? I don't
recall this being an operator for the Streaming API. If you're passing it as
some kind of analogue to a source parameter you'd pass in basic auth on
tweet creation, it's unnecessary here unless there's some other use
Hi Taylor,
Finally! It now works. TweetSharp includes the source parameter by
default on all requests (I think). Thus, I overrode the
TwitterClientInfo just for that request and cleared out the
ClientName field. Now it works!
I guess on your side, the code filters out unknown parameters before
Wil,
Fantastic. So glad you got it working, and thanks for sharing the solution
which worked for you.
Matt
On Mon, Jun 28, 2010 at 10:10 AM, Wil willi...@gmail.com wrote:
Hi Taylor,
Finally! It now works. TweetSharp includes the source parameter by
default on all requests (I think). Thus,
Hi,
@John: I removed the delimited=1 parameter and it still gave me 401's.
@Taylor: I checked my system clock and does not differ from the server
time by more than 5 minutes.
The code works with the following which I've used:
1) OAuth authentication methods
2) statuses/user_timeline
3)
Just a short follow-up:
I tried the streaming API again with OAuth and statuses/sample
(instead of statuses/filter) and it works...
however the statuses/filter still doesn't work (I get 401) even if I
access the stream using the same account.
Thanks,
Wil
On Jun 26, 5:50 am, Taylor Singletary
An invalid delimited parameter is ignored, and won't cause a 401.
On Sat, Jun 26, 2010 at 2:04 AM, Wil willi...@gmail.com wrote:
Hi,
@John: I removed the delimited=1 parameter and it still gave me 401's.
@Taylor: I checked my system clock and does not differ from the server
time by more
Hi,
Sorry it took me a while since I'm using TweetSharp and am stepping
through the (unfamiliar) code.
The moment you said about the signature, I'm suspecting that the
problem is somewhere with that. However, I got this:
POSThttp%3A%2F%2Fstream.twitter.com%2F1%2Fstatuses
Hi John,
Uhh, care to elaborate? I don't quite get what you meant...
Thanks,
Wil
On Jun 24, 11:17 pm, John Kalucki j...@twitter.com wrote:
Aside from the oAuth issue, which others can address, the only valid
delimited value is length.
-John
On Thu, Jun 24, 2010 at 7:58 AM, Wil
Wil,
Does your OAuth code work against other aspects of the Twitter API? Can you
verify if your system's clock is within 5 minutes or so of the times
returned by our system? (You can see the current server time in an HTTP
header of any of our responses).
Are you sure that your code is actually
I'm getting this response:
HTTP/1.1 401 Unauthorized
Content-Length: 1296
Cache-Control: must-revalidate,no-cache,no-store
Content-Type: text/html; charset=iso-8859-1
Server: Jetty(6.1.17)
WWW-Authenticate: Basic realm=Firehose
html
head
meta http-equiv=Content-Type content=text/html;
Aside from the oAuth issue, which others can address, the only valid
delimited value is length.
-John
On Thu, Jun 24, 2010 at 7:58 AM, Wil willi...@gmail.com wrote:
I'm getting this response:
HTTP/1.1 401 Unauthorized
Content-Length: 1296
Cache-Control: must-revalidate,no-cache,no-store
Hi Wil,
I can help you with the OAuth component of this. Can you share your
signature base string for the request?
Here's an example of a few of the steps of a functioning OAuth request
against this endpoint:
POST body
source=softwarenamedelimited=1follow=156934710
Signature Base String
I'm a bit dumbfounded here...
I've been trying to login to stream.twitter.com using OAuth
(particularly, I've been trying to access
http://stream.twitter.com/1/statuses/filter.json?follow=). I used
the access keys obtained from https://api.twitter.com/oauth/access_token
however, I've been
OAuth should work fine on stream.twitter.com
-John Kalucki
http://twitter.com/jkalucki
Infrastructure, Twitter Inc.
On Tue, Jun 22, 2010 at 10:00 AM, Wil willi...@gmail.com wrote:
I'm a bit dumbfounded here...
I've been trying to login to stream.twitter.com using OAuth
(particularly, I've
Hi,
Is there an ETA for enabling oauth on stream.twitter.com?
Thanks,
Aaron
On May 13, 1:11 pm, John Kalucki j...@twitter.com wrote:
OAuthis not enabled on stream.twitter.com. You can try on
chirpstream.twitter.com.
On Thu, May 13, 2010 at 10:53 AM, Lucas Vickers lucasvick...@gmail.com
OAuth is now enabled on stream.twitter.com. I'll also send a note out
to the announce list
---Mark
http://twitter.com/mccv
On Mon, May 24, 2010 at 12:30 PM, Aaron Rankin aran...@gmail.com wrote:
Hi,
Is there an ETA for enabling oauth on stream.twitter.com?
Thanks,
Aaron
On May
Does this mean that the streaming API will also make the switch from
basic authentication to OAuth at the end of June?
On Mon, May 24, 2010 at 4:50 PM, Mark McBride mmcbr...@twitter.com wrote:
OAuth is now enabled on stream.twitter.com. I'll also send a note out
to the announce list
We haven't announced our plans for streaming and oAuth, beyond stating that
User Streams will only be on oAuth.
On Mon, May 24, 2010 at 1:57 PM, 140dev 140...@gmail.com wrote:
Does this mean that the streaming API will also make the switch from
basic authentication to OAuth at the end of
Hey we need documentation!
Jonathon
On May 24, 4:50 pm, Mark McBride mmcbr...@twitter.com wrote:
OAuth is now enabled on stream.twitter.com. I'll also send a note out
to the announce list
---Mark
http://twitter.com/mccv
On Mon, May 24, 2010 at 12:30 PM, Aaron Rankin
The format is fairly simple and almost self explanatory.
Check out this for a working sample:
http://github.com/zbowling/earlybird
Zac Bowling
On Mon, May 24, 2010 at 7:23 PM, Jonathon Hill jhill9...@gmail.com wrote:
Hey we need documentation!
Jonathon
On May 24, 4:50 pm, Mark McBride
I am writing my own c++ based OAuth library. I know there is liboauth
but I like to do things myself to learn.
Anyhow I am trying to access http://stream.twitter.com/1/statuses/sample.xml
and I keep getting 401.
I have verified pretty much every parameter, and used the tool on
OAuth is not enabled on stream.twitter.com. You can try on
chirpstream.twitter.com.
On Thu, May 13, 2010 at 10:53 AM, Lucas Vickers lucasvick...@gmail.com wrote:
I am writing my own c++ based OAuth library. I know there is liboauth
but I like to do things myself to learn.
Anyhow I am trying
Excellent, it works!
thanks
On Thu, May 13, 2010 at 2:11 PM, John Kalucki j...@twitter.com wrote:
OAuth is not enabled on stream.twitter.com. You can try on
chirpstream.twitter.com.
On Thu, May 13, 2010 at 10:53 AM, Lucas Vickers lucasvick...@gmail.com
wrote:
I am writing my own c++
Thanks Taylor for the very detailed and helpful response!
Jonathon
On Apr 20, 1:17 pm, Taylor Singletary taylorsinglet...@twitter.com
wrote:
Hi Jonathon,
For Streaming API access that isn't from the perspective of a user's
account, you would use two-legged OAuth to establish authentication
34 matches
Mail list logo
