Yahoo! Pipes unable to access Twitter feeds.
51 views
Skip to first unread message
pjdonnelly
Jul 21, 2008, 1:46:35 PM7/21/08
to Twitter Development Talk, pipe...@yahoo-inc.com
Hi,
Our Yahoo! Pipe developers have been reporting a lot of 406 errors.
Can anyone in Twitter shed some light on the issue, and if its
business related, let us know who we should contact?
Thanks -Paul
Pipes Team.
Our Yahoo! Pipe developers have been reporting a lot of 406 errors.
Can anyone in Twitter shed some light on the issue, and if its
business related, let us know who we should contact?
Thanks -Paul
Pipes Team.
Alex Payne
Jul 21, 2008, 6:07:04 PM7/21/08
to twitter-deve...@googlegroups.com, pipe...@yahoo-inc.com
We're handling this off-list, I think. For the record, we don't
explicitly throw 406 errors from our application. They could be from
either httpd or our load balancer.
explicitly throw 406 errors from our application. They could be from
either httpd or our load balancer.
--
Alex Payne
http://twitter.com/al3x
Kent Brewster
Jul 21, 2008, 5:26:10 PM7/21/08
to Twitter Development Talk
Paul: are your developers hitting the unauthenticated APIs? If so,
they are being rate-limited out of existence. I ran into this one
myself; it's why Twitterati quit working.
--Kent
they are being rate-limited out of existence. I ran into this one
myself; it's why Twitterati quit working.
--Kent
brainwipe
Jul 23, 2008, 6:15:01 AM7/23/08
to Twitter Development Talk
I'm a Yahoo Pipes Dev who is getting a lot of 406 errors. I'm
aggregating from the standard RSS feeds that can be found on the
Twitter homepage.
Am I polling too often from Pipes?
Rob Lang
On Jul 21, 10:26 pm, Kent Brewster <kentb...@gmail.com> wrote:
> Paul: are your developers hitting the unauthenticated APIs? If so,
> they are being rate-limited out of existence. I ran into this one
> myself; it's why Twitterati quit working.
>
> --Kent
>
> On Jul 21, 10:46 am, pjdonnelly <pjdonne...@gmail.com> wrote:
>
> > Hi,
>
> > OurYahoo! Pipe developers have been reporting a lot of 406 errors.
aggregating from the standard RSS feeds that can be found on the
Twitter homepage.
Am I polling too often from Pipes?
Rob Lang
On Jul 21, 10:26 pm, Kent Brewster <kentb...@gmail.com> wrote:
> Paul: are your developers hitting the unauthenticated APIs? If so,
> they are being rate-limited out of existence. I ran into this one
> myself; it's why Twitterati quit working.
>
> --Kent
>
> On Jul 21, 10:46 am, pjdonnelly <pjdonne...@gmail.com> wrote:
>
> > Hi,
>
Alex Payne
Jul 23, 2008, 12:53:30 PM7/23/08
to twitter-deve...@googlegroups.com
We don't return 406 when you're polling too often; we return it for
invalid MIME types in requests.
invalid MIME types in requests.
--
Alex Payne
http://twitter.com/al3x
brainwipe
Jul 25, 2008, 12:09:42 PM7/25/08
to Twitter Development Talk
Ah, interesting. I am using the standard Yahoo Pipe for grabbing RSS
feeds, so I can't say what the MIME type is.
Rob
feeds, so I can't say what the MIME type is.
Rob
Jonathan
Jul 28, 2008, 4:02:49 PM7/28/08
to Twitter Development Talk
Based on our testing it appears not an issue with the mime type.
Simple "curl" requests from a variety of servers other than our
outbound HTTP proxy servers work successfully. The same requests
originating on our proxy servers return 406's. I'd guess that
something in Twitters infrastructure is denying based on IP.
Jonathan
On Jul 25, 9:09 am, brainwipe <brainwi...@googlemail.com> wrote:
> Ah, interesting. I am using the standardYahooPipe for grabbing RSS
Simple "curl" requests from a variety of servers other than our
outbound HTTP proxy servers work successfully. The same requests
originating on our proxy servers return 406's. I'd guess that
something in Twitters infrastructure is denying based on IP.
Jonathan
On Jul 25, 9:09 am, brainwipe <brainwi...@googlemail.com> wrote:
> Ah, interesting. I am using the standardYahooPipe for grabbing RSS
efrenefren
Aug 6, 2008, 9:35:10 AM8/6/08
to Twitter Development Talk
So is there a fix or a workaround for this?
Alex Payne
Aug 6, 2008, 12:54:20 PM8/6/08
to twitter-deve...@googlegroups.com
A fix will be deployed today.
--
Alex Payne
http://twitter.com/al3x
Kent Brewster
Aug 6, 2008, 1:01:41 PM8/6/08
to Twitter Development Talk
Can you say more about the fix, please? It sounds like Pipes users
will be able to make unlimited calls to the unauthenticated Twitter
APIs again, which would be really, really sweet, and well worth
blogging about.
--Kent
will be able to make unlimited calls to the unauthenticated Twitter
APIs again, which would be really, really sweet, and well worth
blogging about.
--Kent
Alex Payne
Aug 6, 2008, 1:16:12 PM8/6/08
to twitter-deve...@googlegroups.com
Well, the initial fix is for the 406 issue. When that's resolved,
Pipes users will still run into the rate limit. If you contact me
off-list with the IPs that Pipes uses, I'll look into adding IP-based
whitelisting so we can get this working again.
Pipes users will still run into the rate limit. If you contact me
off-list with the IPs that Pipes uses, I'll look into adding IP-based
whitelisting so we can get this working again.
--
Alex Payne
http://twitter.com/al3x
Kent Brewster
Aug 7, 2008, 2:00:51 PM8/7/08
to Twitter Development Talk
I'll ask Jonathan to ping you with those IPs, Alex, thanks.
--Kent
On Aug 6, 10:16 am, "Alex Payne" <a...@twitter.com> wrote:
> Well, the initial fix is for the 406 issue. When that's resolved,
> Pipes users will still run into the rate limit. If you contact me
> off-list with the IPs that Pipes uses, I'll look into adding IP-based
> whitelisting so we can get this working again.
>
--Kent
On Aug 6, 10:16 am, "Alex Payne" <a...@twitter.com> wrote:
> Well, the initial fix is for the 406 issue. When that's resolved,
> Pipes users will still run into the rate limit. If you contact me
> off-list with the IPs that Pipes uses, I'll look into adding IP-based
> whitelisting so we can get this working again.
>
efrenefren
Aug 8, 2008, 10:56:48 AM8/8/08
to Twitter Development Talk
It now returns a 400 Bad Request Error in Yahoo Pipes
On Aug 8, 2:00 am, Kent Brewster <kentb...@gmail.com> wrote:
> I'll ask Jonathan to ping you with those IPs, Alex, thanks.
>
> --Kent
>
> On Aug 6, 10:16 am, "Alex Payne" <a...@twitter.com> wrote:
>
> > Well, the initial fix is for the 406 issue. When that's resolved,
> >Pipesusers will still run into the rate limit. If you contact me
> > off-list with the IPs thatPipesuses, I'll look into adding IP-based
On Aug 8, 2:00 am, Kent Brewster <kentb...@gmail.com> wrote:
> I'll ask Jonathan to ping you with those IPs, Alex, thanks.
>
> --Kent
>
> On Aug 6, 10:16 am, "Alex Payne" <a...@twitter.com> wrote:
>
> > Well, the initial fix is for the 406 issue. When that's resolved,
> > off-list with the IPs thatPipesuses, I'll look into adding IP-based
Alex Payne
Aug 8, 2008, 1:08:09 PM8/8/08
to twitter-deve...@googlegroups.com
Yes, that is the expected behavior. They're running into the IP-based
rate limit for unauthenticated requests. We'll be whitelisting their
IPs shortly.
rate limit for unauthenticated requests. We'll be whitelisting their
IPs shortly.
--
Alex Payne
http://twitter.com/al3x
Kent Brewster
Aug 22, 2008, 6:19:06 PM8/22/08
to Twitter Development Talk
The whitelist form has been submitted with those Pipes IPs; hopefully
we will be working soon.
--Kent
we will be working soon.
--Kent
efrenefren
Sep 2, 2008, 7:47:06 PM9/2/08
to Twitter Development Talk
Accessing a twitter feed from yahoo pipes still returns a 400 Bad
Request. What does that mean?
On Aug 23, 6:19 am, Kent Brewster <kentbrews...@gmail.com> wrote:
> The whitelist form has been submitted with thosePipesIPs; hopefully
Request. What does that mean?
On Aug 23, 6:19 am, Kent Brewster <kentbrews...@gmail.com> wrote:
> The whitelist form has been submitted with thosePipesIPs; hopefully
Alex Payne
Sep 3, 2008, 12:48:37 PM9/3/08
to twitter-deve...@googlegroups.com
It means we still haven't figured out why they're not on our
whitelist. We'll be looking into it.
whitelist. We'll be looking into it.
--
Alex Payne - API Lead, Twitter, Inc.
http://twitter.com/al3x
efrenefren
Sep 16, 2008, 3:48:06 AM9/16/08
to Twitter Development Talk
Just a twitter feed in yahoo and it works!
> OurYahoo! Pipe developers have been reporting a lot of 406 errors.
> OurYahoo! Pipe developers have been reporting a lot of 406 errors.
Reply all
Reply to author
Forward
0 new messages