riginal Message-
> From: twitter-development-talk@googlegroups.com
>
> [mailto:twitter-development-t...@googlegroups.com] On Behalf Of John
> Kalucki
> Sent: Wednesday, September 16, 2009 12:56
> To: Twitter Development Talk
> Subject: [twitter-dev] Re: non json response
>
> I&#x
bject: [twitter-dev] Re: non json response
I've been following the internal dialog on tracking this issue down.
Given what we know, I don't think there's anything that you can change
to the request parameters to reduce the chances of this happening.
>From a given client, the ch
I've been following the internal dialog on tracking this issue down.
Given what we know, I don't think there's anything that you can change
to the request parameters to reduce the chances of this happening.
>From a given client, the chances of this happening to a request are
pretty close to random
hi naveen.
we are most certainly working on it.
the best way to mitigate the error case is to actually do what the
response tells you to do -- in all cases that i've seen the "http 200
error", there has been a refresh header ("Refresh: 0.1"). simply obey
the header, make a subsequent req
Is there a specific way we can construct our request to mitigate the
non-json response? I have used a few different twitter clients on the
same mobile device and some of them do not seem to be plagued with the
bad data like we are? Does including something in the header help get
us through whateve
I just had one non-json response, in the middle of about 10 requests
made with curl -vvv (other responses were correct)
Below are 3 requests and the non-json response bracketted by 2 good
responses which contain the response time and other logging data.
HTH
Rudi
rudolf-farkass-macbook-pro:Twit
Hi all.
This is an extremely high priority problem for us, and for me
personally, to fix.
If you're having this problem, please free to reach out to me, but
please try to include:
* the IP address your request is coming from
* the request you're making
* the response you got back
* the t
I'm seeing tons of these as well.
However, I've found that if you follow the suggestion of the META tag to
simply "refresh" in 0.1 seconds if you get this bogus response, you can hide
most of this from users, especially if they are on a fast network.
On Thu, Sep 10, 2009 at 2:09 PM, Monica Keller
People are working on this as a high-priority issue. I'd imagine that
the API team will have an update soon.
On Sep 10, 2:09 pm, Monica Keller wrote:
> We see this error 75% of the time. Have you guys made an progress on
> resolving the issue ?
>
> On Sep 6, 8:14 pm, archF6 wrote:
>
> > I am ab
We see this error 75% of the time. Have you guys made an progress on
resolving the issue ?
On Sep 6, 8:14 pm, archF6 wrote:
> I am able to consistently reproduce this error. I am making GET
> requests via PHP from IP: 96.30.16.192. I receive the error without
> fail after periods of inactivity
I am able to consistently reproduce this error. I am making GET
requests via PHP from IP: 96.30.16.192. I receive the error without
fail after periods of inactivity lasting 2 hours or more. The header
response code is 200. Please let me know if I can provide any
additional info that might help
I am able to consistently reproduce this error -- I get this response
almost without fail after periods of inactivity greater than 2 hours.
I am requesting XML via PHP, it's a GET request. The requests are
coming from 96.30.16.192. Let me know if I can provide any additional
info that might help
Either way an XML or JSON feed should NEVER return HTML!
On Sep 7, 11:25 am, Ben Eliott wrote:
> IP: 67.23.28.168, time is Europe/London
>
> 2009-09-07 11:19:48,014 - twittersearch.models - CRITICAL - Search did
> not reutrn a json object! code = 200 answer = "-//W3C//DTD HTML 4.01//EN"
> "h
IP: 67.23.28.168, time is Europe/London
2009-09-07 11:19:48,014 - twittersearch.models - CRITICAL - Search did
not reutrn a json object! code = 200 answer = "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/1999/REC-html401-19991224/strict.dtd
">
Starting to wonder whether this i
I think this is the same issue we've been having for a while at
http://groups.google.com/group/twitter-development-talk/browse_thread/thread/e88f0f3182b0a0e7/e5f6b2a5678598f1
I never used to get it on search APIs but now I get it on both REST
and search APIs
On Sep 6, 8:35 pm, Rudifa wrote:
> I
I have seen this same http page with empty body
http://www.w3.org/
TR/1999/REC-html401-19991224/strict.dtd">
a number of times in the last few days (but intermittently - a good
response may come after several attempts),
in response to http://twitter.com/users/show/rudifa.json
The most r
I'm consistently getting the same response when accessing
http://search.twitter.com/trends.json from 209.40.204.183
Steve
On Aug 26, 5:27 pm, Ryan Sarver wrote:
> Ben,
>
> It's a known issue and we are trying to hunt it down. Can you please
> provide us with your source IP and an approximate ti
Hi,
Just wanted to add that this problem is not restricted to json, but
exists with the atom api too. I'll try to find some more info. Will
post it here if I get it. It has happened previously too. We had to
write a function to prevent to check for html and if yes prevent it
from being parsed by
Hi,
Just got hold of a log entry. We had this issue on Friday, August 28,
2009 - 11:02am Indian Standard Time (+0530 UTC). Our site is
brandadda.com .
Hope this is useful.
Best,
Anirudh S
On Aug 26, 9:27 pm, Ryan Sarver wrote:
> Ben,
>
> It's a known issue and we are trying to hunt it down.
H Ryan,
Thanks for coming back on this. Here's a bit of logging which has the
url query and the precise time of the returned search, the timezone is
Europe/London. The ip is 67.23.28.168. I might be able to get more for
other times, let me know if you need 'em. This app is in development
s
Ben,
It's a known issue and we are trying to hunt it down. Can you please
provide us with your source IP and an approximate time of when you saw
it?
Thanks, Ryan
On Wed, Aug 26, 2009 at 7:00 AM, ben wrote:
>
> Occassionally i get back a 200 status html response from the json
> search api which
21 matches
Mail list logo
