An HTTP 404 is the correct response because you are attempting to access a nonexistent resource. This behavior is correctly documented here [1].
1. http://apiwiki.twitter.com/HTTP-Response-Codes-and-Errors Doug Williams Twitter API Support http://twitter.com/dougw On Thu, Apr 23, 2009 at 9:03 AM, Yusuke <[email protected]> wrote: > > Hi, > > I noticed that now the API returns 404 status code when a client > called /friendships/create/[non-existing-user].xml. > The API used to be returning 403 status code. > Will it be a permanent behavior? Or is it subject to change? > > I'll be nice if the status codes in exceptional cases are explicitly > documented so that client developers can confidently implement error > handling codes. > > Cheers, > Yusuke >
