Hi Taylor,
Great! Worked like a charm with commas doubly encoded.
Thanks,
Kostya
On Jul 21, 7:34 pm, Taylor Singletary
wrote:
> Hi Kostya,
>
> You're close on getting the comma-separation to work. You've correctly
> URL encoded it for your POST body, but for the OAuth signature base
> string,
Hi Kostya,
You're close on getting the comma-separation to work. You've correctly
URL encoded it for your POST body, but for the OAuth signature base
string, it'll need to be doubly encoded.
Your base string should be something like:
POST&http%3A%2F%2Fstream.twitter.com%2F1%2Fstatuses
%2Ffilter.j
Matt,
Another question I believe you may clarify.
Streaming API over OAuth works fine if track only one item:
"track=sun"
When I want to track multiple items like "track=sun,microsoft" I'm
getting 401
There is what I'm sending:
POST /1/statuses/filter.json HTTP/1.1\r\nHost: stream.twitter.com\r
Hi Matt,
Very appreciate your response!
It is working now after I quoted the oauth values.
So, the quoting matters.
Also, Consumer token was in place of OAuth one, and vice versa.
Thanks a lot,
Kostya
On Jul 21, 1:13 am, Matt Harris wrote:
> Hey Kostya,
>
> I've taken a quick look at your POS
Hey Kostya,
I've taken a quick look at your POST headers and noticed a couple of things:
1) Whilst it shouldn't matter the streaming API can be very particular about
the headers you send so I recommend you quote your OAuth values,
e.g. oauth_nonce="Rb34D3rVEetj"
2) Your OAuth token looks like a
Hi Kostya,
I'm unable to reproduce your issue, unfortunately. Are you still getting a
500 error when trying to connect to streaming via OAuth? Have you tried
using a different access token or even API key? Does the same code/keys work
against the REST API?
Taylor
On Tue, Jul 20, 2010 at 2:58 PM,
Taylor,
Did the details I posted help to identify the issue?
Thanks,
Kostya
On Jul 20, 9:56 pm, ap wrote:
> Looks like the oAuth access token issue is back! Started getting 500's
> from Twitter API a few minutes ago.
>
> On Jul 20, 11:38 am, Kostya Nikolayev wrote:
>
> > Taylor!
>
> > This is
Taylor,
Looks like things are back to normal now.
Thanks!
On Jul 20, 4:59 pm, Taylor Singletary
wrote:
> We may have had a hiccup period as we finished correcting last night's
> remaining issues. Are you still seeing the 500s?
>
> On Tue, Jul 20, 2010 at 11:56 AM, ap wrote:
> > Looks like the
We may have had a hiccup period as we finished correcting last night's
remaining issues. Are you still seeing the 500s?
On Tue, Jul 20, 2010 at 11:56 AM, ap wrote:
> Looks like the oAuth access token issue is back! Started getting 500's
> from Twitter API a few minutes ago.
>
> On Jul 20, 11:38
Looks like the oAuth access token issue is back! Started getting 500's
from Twitter API a few minutes ago.
On Jul 20, 11:38 am, Kostya Nikolayev wrote:
> Taylor!
>
> This is what I'm sending:
>
> POST /1/statuses/filter.json HTTP/1.1\r\nHost: stream.twitter.com\r
> \nUser-Agent: TweetStream\r\nAu
Taylor!
This is what I'm sending:
POST /1/statuses/filter.json HTTP/1.1\r\nHost: stream.twitter.com\r
\nUser-Agent: TweetStream\r\nAuthorization: OAuth
oauth_nonce=0IblKRcN17LUBG6zMnQk6DVrObhzcZowIVpPLtsRviU,
oauth_signature=rbGAlSp1VIbuXbk4Wr99jumyi5o%3D,
oauth_signature_method=HMAC-SHA1, oauth_
Hi Kostya,
I'm able to connect to the streaming API over OAuth fine at the moment.
Can you share the full URL, HTTP method, and parameters that you are trying
to access? If possible, also your signature base string?
Taylor
On Tue, Jul 20, 2010 at 8:09 AM, Kostya Nikolayev wrote:
> Taylor,
>
>
Taylor,
Has Sreaming API OAuth been affected ?
Authenticating with the following oauth header gives 500 to me:
"OAuth oauth_nonce=N9wgHt2uPw8HqRwtOpjuVDSeuVYmc8UGDF8H0237v0,
oauth_signature=ALUT7tKXK%2Fw57SnJulj8x1l%2F7%2Fk%3D,
oauth_signature_method=HMAC-SHA1, oauth_timestamp=1279638245,
oauth_c
I think its now fixed
On Jul 20, 3:41 pm, acreadinglist wrote:
> Add me to the list.
>
> On Jul 19, 7:24 pm, JeremyE wrote:
>
> > I'm having the same exact issue while developing my app. Internal
> > Server Error 500 from Twitter. Trying to get my access token.
Add me to the list.
On Jul 19, 7:24 pm, JeremyE wrote:
> I'm having the same exact issue while developing my app. Internal
> Server Error 500 from Twitter. Trying to get my access token.
I'm having the same exact issue while developing my app. Internal
Server Error 500 from Twitter. Trying to get my access token.
Same here.
Worked fine in the morning, I thought my app was set for the day (I
just released a new version) but then when I tried it myself later, I
stumbled on this issue.
It's pretty bad since I was releasing a new version today and was
hoping for it to gain much momentum. I looked for a mistak
Yup.
it's down. has been for hours.
users of my app can't log in / authenticate their twitter accounts.
If they're already logged in, they're fine. ie: other API calls work.
On Jul 19, 4:02 pm, cyclemenow wrote:
> I'm unable to use my own app!
>
> The status page implies that everything is up
On Tue, Jul 20, 2010 at 1:02 AM, cyclemenow wrote:
> I'm unable to use my own app!
same here.
I'm unable to use my own app!
The status page implies that everything is up right now (http://
dev.twitter.com/status).
I haven't been able to use OAuth almost the entire day.
Does this issue affect everybody? Are there any workarounds?
-Matthew
On Jul 19, 3:10 pm, CJ wrote:
> Hi Ap,
>
> I th
Hi Ap,
I thought I've broken my software. I had exactly the same error
message after my software performed a HTTP GET for "/oauth/
access_token?oauth_token=.&oauth_verifier=PIN".
Hope this issue can be resolved asap.
CJ
On Jul 19, 10:04 pm, Tim Davies wrote:
> I've also been having this is
I've also been having this issue solidly for the last 5 hrs.
ap,
I'm experiencing the problem too. It's good to hear that Taylor et al
are on the case.
23 matches
Mail list logo
