Hi, I've experienced a few 404's on search.json this morning.
Sometimes works, sometimes doesn't can't seem to pinpoint any particular pattern to it happening. -- Leu On Apr 17, 5:11 am, Chad Etzel <jazzyc...@gmail.com> wrote: > Just a quick update: > > The problem as popped up again. Doug is aware of this problem, and he > says the servers are all stretched pretty thin (understandable). Just > curious if anyone else is seeing this as well? > > -Chad > > On Thu, Apr 16, 2009 at 11:30 PM, Chad Etzel <jazzyc...@gmail.com> wrote: > > Ok, dunno what was happening... I gave my server a swift kick with my > > steel-toed boot and all seems well again... weird. > > -Chad > > > On Thu, Apr 16, 2009 at 10:27 PM, Doug Williams <d...@twitter.com> wrote: > >> I just sent 200 queries through without seeing the 404. Are you still > >> seeing > >> this? > > >> Doug Williams > >> Twitter API Support > >>http://twitter.com/dougw > > >> On Thu, Apr 16, 2009 at 6:32 PM, Chad Etzel <jazzyc...@gmail.com> wrote: > > >>> Search is throwing 404's for search.json about every 7 or 8 requests... > > >>> <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> > >>> <html><head> > >>> <title>404 Not Found</title> > >>> </head><body> > >>> <h1>Not Found</h1> > >>> <p>The requested URL /search.json was not found on this server.</p> > >>> </body></html> > > >>> Also got a "Forbidden" return when trying to connect to > >>>http://search.twitter.com/about 10 minutes ago. > > >>> -Chad
