Thread:Talk:Requests for comment/API Future/HTTP errors/reply

Yes, it was proposed on IRC, and for a while I thought it would be a good idea, but even for the case of errors, this might be limiting, i.e. error due to servers too busy (lag) should not mark this URL as invalid in various caches. Unless we want to find an HTTP error code for each error api may produce. Most would be 400, non-logged in/tokens - 401, 409 - edit conflict, ... Probably all this is not worth it. Removing.