Re: [twitter-dev] friendships/create method and 403 ambiguity

2009-12-15 Thread Marcel Molina
In the long term we plan to add internal error codes to every non 2** response so that the consumer can unambiguously know what error they got without munging error message strings (who's language might be changed innocently not knowing the consequences). On Mon, Dec 14, 2009 at 2:42 PM, Mark

Re: [twitter-dev] friendships/create method and 403 ambiguity

2009-12-15 Thread shiplu
On Wed, Dec 16, 2009 at 6:02 AM, Marcel Molina mar...@twitter.com wrote: In the long term we plan to add internal error codes to every non 2** response so that the consumer can unambiguously know what error they got without munging error message strings (who's language might be changed

[twitter-dev] friendships/create method and 403 ambiguity

2009-12-14 Thread shiplu
There are two phrases about friendships/create. 1. If you are already friends with the user an HTTP 403 will be returned. 2. This method is subject to [1]update limits. An HTTP 403 will be returned if this limit as been hit. How to differ those two status codes? [1]

Re: [twitter-dev] friendships/create method and 403 ambiguity

2009-12-14 Thread Mark McBride
The body of the response allows you to differentiate these two codes, e.g. curl -ucredentials -XPOST -d http://twitter.com/friendships/create/atebits.xml ?xml version=1.0 encoding=UTF-8? hash request/friendships/create/atebits.xml/request errorCould not follow user: atebits is already on