Information ok thak you Alcides Conceiçao dos Santos Country : Brazil 2010/1/27 Jeffrey Greenberg <jeffreygreenb...@gmail.com>: > hmmm... i'm not seeing 500 errors anymore... either > > transient problem? > > j > > On Jan 26, 5:18 pm, Kevin Marshall <falico...@gmail.com> wrote: >> That's what I see as well. >> >> - Kevinhttp://wow.ly >> >> >> >> On Tue, Jan 26, 2010 at 7:48 PM, Raffi Krikorian <ra...@twitter.com> wrote: >> > i'm confused - what are people seeing? i'm seeing a 404 on that status, >> > not >> > a 500. >> > [ra...@tw-mbp13-raffi twitter (homing_pigeon)]$ curl -v >> >http://twitter.com/statuses/show/15527375.xml >> > * About to connect() to twitter.com port 80 (#0) >> > * Trying 168.143.162.68... connected >> > * Connected to twitter.com (168.143.162.68) port 80 (#0) >> >> GET /statuses/show/15527375.xml HTTP/1.1 >> >> User-Agent: curl/7.16.3 (powerpc-apple-darwin9.0) libcurl/7.16.3 >> >> OpenSSL/0.9.7l zlib/1.2.3 >> >> Host: twitter.com >> >> Accept: */* >> >> > < HTTP/1.1 404 Not Found >> > < Date: Wed, 27 Jan 2010 00:47:26 GMT >> > < Server: hi >> > < X-RateLimit-Limit: 20000 >> > < X-Transaction: 1264553246-49270-7281 >> > < Status: 404 Not Found >> > < Last-Modified: Wed, 27 Jan 2010 00:47:26 GMT >> > < X-RateLimit-Remaining: 19765 >> > < X-Runtime: 0.02460 >> > < Content-Type: application/xml; charset=utf-8 >> > < Pragma: no-cache >> > < Content-Length: 150 >> > < X-RateLimit-Class: api_whitelisted >> > < Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, >> > post-check=0 >> > < Expires: Tue, 31 Mar 1981 05:00:00 GMT >> > < X-Revision: DEV >> > < X-RateLimit-Reset: 1264555010 >> > < Set-Cookie: >> > _twitter_sess=BAh7CToOcmV0dXJuX3RvIjJodHRwOi8vdHdpdHRlci5jb20vc3RhdHVzZXMv% >> > >> > 250Ac2hvdy8xNTUyNzM3NS54bWw6EXRyYW5zX3Byb21wdDA6B2lkIiVkYTI3NTQ0%250AODg1NW >> > >> > I1M2U2YmE0ZDk3ZjUzYTRkOTYyNSIKZmxhc2hJQzonQWN0aW9uQ29u%250AdHJvbGxlcjo6Rmxh >> > >> > c2g6OkZsYXNoSGFzaHsABjoKQHVzZWR7AA%253D%253D--c18561191b4733080388d38fa9461 >> > b6f851b16dc; >> > domain=.twitter.com; path=/ >> > < Vary: Accept-Encoding >> > < Connection: close >> > < >> > <?xml version="1.0" encoding="UTF-8"?> >> > <hash> >> > <request>/statuses/show/15527375.xml</request> >> > <error>No status found with that ID.</error> >> > </hash> >> > * Closing connection #0 >> >> > On Tue, Jan 26, 2010 at 4:44 PM, Jeffrey Greenberg >> > <jeffreygreenb...@gmail.com> wrote: >> >> >> To be accurate: most ids do work... We had no httpstatus 500 errors >> >> for quite a while, so this is new and different and bad behavior. >> >> We've had a working application that has been functioning for more >> >> than a year, and way back when these errors were frequent, and then >> >> Twitter did alot of new/good work and they've all but gone away (at >> >> least on this api)... until now. >> >> . >> >> >> On Jan 26, 12:39 pm, Kevin Marshall <falico...@gmail.com> wrote: >> >> > Yes - seems to be a problem for any id other than the example one in >> >> > the documentation: >> >> >> >http://twitter.com/statuses/show/1472669360.xml(works) >> >> >> >http://twitter.com/statuses/show/12735452.xml(reportsno statuses, >> >> > but this is my account and so I can confirm that there are statuses >> >> > there to report -- ashttp://twitter.com/users/show.xml?id=12735452 >> >> > also confirms). >> >> >> > BTW - if you use the user_timeline method, I think you can get the >> >> > same status stuff >> >> > (http://twitter.com/statuses/user_timeline.xml?id=12735452) >> >> >> > - Kevin >> >> >> > On Tue, Jan 26, 2010 at 3:11 PM, Jeffrey Greenberg >> >> >> > <jeffreygreenb...@gmail.com> wrote: >> >> > > For instance:http://twitter.com/statuses/show/15527375.xml >> >> >> > > anyone else seeing these? >> >> > -- >> > Raffi Krikorian >> > Twitter Platform Team >> >http://twitter.com/raffi >
-- Alcides conceição dos Santos
