> > > The error code for search rate limiting will be changing from HTTP > > > 503 to HTTP 401 in the very near future (today or tomorrow). For > > > details, continue reading. > > > > Are you sure you want to use 401 for this? 401 would indicate authorization > > required. If you're asking for credentials, that would make sense, but if > > you're not, I would think the 503 is still the proper response irrespective > > of broken proxies. I don't see other codes that have that one's temporal > > semantics. > > We use 400 for rate limiting on the REST API. Matt and I are > discussing whether or not this might be the correct response. > Thoughts?
I guess that would work there too IMHO. It's ill-defined but that's a bonus in this case :) -- ------------------------------------ personal: http://www.cameronkaiser.com/ -- Cameron Kaiser * Floodgap Systems * www.floodgap.com * [EMAIL PROTECTED] -- Logic is the art of going wrong with confidence. -- George Bernard Shaw ----
