Skip to content

Provide proper status codes for API operations #2187

@javorszky

Description

@javorszky

@halfdan linked me http://tools.ietf.org/html/rfc2616. I was thinking whether it'd be a good idea / OCD / doing it right thing if we provided the proper status codes for API responses. Currently we're using 500, 404, 415, 413, 403, 401 and 200 (along with the 304 for caching).

The RFC allows for more granular bits, like

  • 201 Created - could be used for new posts / users / tags
  • 202 Accepted - could be used to get back to the browser once data is here, but before promises resolve and a proper response gets back (not sure though)

Thoughts?

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions