Hi all,
The issue with random HTTP 403s on search (both API and web)
should now be fixed. Similar to the employee password prompts a few
days ago we had a host unexpectedly join the search cluster. We want
more capacity so bad we're actually convincing inanimate objects to
join our cause. ¡Viva La Revolución! Unfortunately the host wasn't
ready for the job it volunteered for … we've put the poor thing out of
its misery.
Thanks;
— Matt
On Apr 17, 2009, at 09:01 AM, Matt Sanford wrote:
Hi all,
We're not seeing the 403s in our normal logs but we've seen a
few in responses. We're looking into the issue and I'll send out
more info when I have it.
— Matt
On Apr 17, 2009, at 07:27 AM, Abraham Williams wrote:
This seems to indicate it too.
The 403 Forbidden HTTP status code indicates that the client was
able to communicate with the server, but the server doesn't let the
user access what was requested.
http://en.wikipedia.org/wiki/HTTP_403
On Fri, Apr 17, 2009 at 07:46, Ivan <[email protected]> wrote:
Hi,
Twitter returns a HTTP 403 if you make a properly authorized follow
request to a user already followed.
That seems like the wrong kind of response. It should return 200,
with
data saying the friendship already existed, no?
Ivan
http://tipjoy.com
--
Abraham Williams | http://the.hackerconundrum.com
Hacker | http://abrah.am | http://twitter.com/abraham
Web608 | Community Evangelist | http://web608.org
This email is: [ ] blogable [x] ask first [ ] private.
Sent from Madison, Wisconsin, United States
