it happens even more often now...
On Sep 9, 3:50 am, Jonathan Smith jonathansmith...@gmail.com wrote:
This happens to me when I do json get requests as well.
It happens very inconsistently during a normal session, but I can
almost always reproduce it if I let the client sit for a while and
We're seeing same error from time to time
Error from Safari when my feeds fail:
Safari can’t open the page “feed://twitter.com/statuses/user_timeline/
18918483.rss”. The error is: “The feed could not be loaded because the
content is not in a known feed format.” (PubSub:2) Please choose
Safari Report Bugs to Apple, note the error number,
I'm also getting these errors.
To get the feed working again, I have to pull up the feed on Safari,
and it will show an error. If I hit refresh, the page will pull new
feeds and my PHP pages which parse the feed also gets refreshed.
-j
On Aug 9, 12:27 am, Chris Babcock cbabc...@asciiking.com
This happens to me when I do json get requests as well.
It happens very inconsistently during a normal session, but I can
almost always reproduce it if I let the client sit for a while and
then try.
Is almost as if the server can't authenticate the request fast enough
and throws back an empty
Can we please hear something from someone at Twitter about this, it's
becoming unusable with constant XML errors
On Sep 7, 4:51 am, Naveen A knig...@gmail.com wrote:
We are seeing this HTML META REFRESH as well from our clients. We are
a mobile application and seeing this issue more and more
It is happening on our site and I checked from one of our other sites
using curl. It gives the 200 error one minute and then the status
response the next. It does not matter if I request JSON it still
returns the HTML.
I am seeing the 200 errors also from our sites. I tried getting
status using curl and it returns the 200 HTML and then the status
intermittently. If I specify JSON I still get the HTML on the errors
and JSON data on the status. This is really affecting our website.
The same also, blank 4.01 .
Hi Ryan,
I am getting the same error - i can found it in the logs of my app
every day - at least 20 times.
1. The IP of the machine making requests to the Twitter API. If you're
behind NAT, please be sure to send us your *external* IP.
---
Name:twittme.mobi
Address: 67.222.129.154
2. The
Yeah it's happening to me again, same as my previous email, except the
time stamp will be around 2 minutes ago
On Sep 6, 4:05 pm, twittme_mobi nlupa...@googlemail.com wrote:
Hi Ryan,
I am getting the same error - i can found it in the logs of my app
every day - at least 20 times.
1. The IP
We are seeing this HTML META REFRESH as well from our clients. We are
a mobile application and seeing this issue more and more frequently to
the point that application is not functioning properly, its hard for
use to provide any specific ip data as the carriers are most likely
proxying the
hi Ryan,
any update on this issue ?
I'm now getting this error back again!
On Aug 18, 4:39 pm, Rich rhyl...@gmail.com wrote:
Thanks Ryan I've emailed the API email address
On Aug 18, 4:21 pm, Ryan Sarver rsar...@twitter.com wrote:
Chris, Rich,
Seems like you aren't the only ones right now. I'm going to work with
Ops to
Rich,
Can you provide your source IP that you are seeing this issue from? We
can only dig into the logs if we know where your traffic is coming
from.
Thanks, Ryan
On Tue, Aug 25, 2009 at 7:19 AM, Richrhyl...@gmail.com wrote:
I'm now getting this error back again!
On Aug 18, 4:39 pm, Rich
Actually it seems to have stabilised at the moment (apart from the
503's that everyone seems to be getting) I'll drop you an email again
if I see it again!
Many thanks
Richard
On Aug 25, 7:13 pm, Ryan Sarver rsar...@twitter.com wrote:
Rich,
Can you provide your source IP that you are seeing
I am seeing this error right now when doing a search. (FWIW: I'm
using since_id)
This is seriously messing things up!
@jeffGreenberg
@tweettronics
Details:
url:
http://search.twitter.com/search.json?q=%23fail%20since%3A2009-08-19rpp=100since_id=3397530515
httpresponse = 200
returned text:
I am seeing this as well on the search api, also sporadically. Where
do I send the details you are requesting?
On Aug 25, 7:18 pm, Jeffrey Greenberg jeffreygreenb...@gmail.com
wrote:
I am seeing this error right now when doing a search. (FWIW: I'm
using since_id)
This is seriously messing
Do you guys notice the api is really slow today? Now the performance
is a little better, but it still slow compare to several days ago.
Thanks
Allan Zhang
On Tue, Aug 25, 2009 at 6:15 PM, Larry Wrightlarrywri...@gmail.com wrote:
I am seeing this as well on the search api, also sporadically.
I'm seeing this type of behaviour too and it's getting very
frustrating.
Basically I'm checking for status 200, then I'm checking for Content-
Type XML. However from time to time I'm getting non XML back from
this function.
On Aug 9, 8:27 am, Chris Babcock cbabc...@asciiking.com wrote:
This
Chris, Rich,
Seems like you aren't the only ones right now. I'm going to work with
Ops to see if we can figure out where it is coming from. Can you
provide us with a little more info so it will be easier to track this
down?
1. The IP of the machine making requests to the Twitter API. If you're
Thanks Ryan I've emailed the API email address
On Aug 18, 4:21 pm, Ryan Sarver rsar...@twitter.com wrote:
Chris, Rich,
Seems like you aren't the only ones right now. I'm going to work with
Ops to see if we can figure out where it is coming from. Can you
provide us with a little more info so
22 matches
Mail list logo
