StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POREST: Mapping application errors to HTTP Status codes
primarykey
Id
2380554
data
AcceptedAnswerId
2381278
AnswerCount
5
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-03-04T15:43:43.987
FavoriteCount
12
LastActivityDate
2010-03-05T15:05:19.417
LastEditDate
2010-03-05T15:05:19.417
LastEditorUserId
23023
OwnerUserId
23023
ParentId
0
PostTypeId
1
Score
35
ViewCount
20771
LastEditorDisplayName
text
Body
Is it to be considered good practice to reuse RFC HTTP Status codes like this, or should we be making up new ones that map exactly to our specific error reasons? We're designing a web service API around a couple of legacy applications. In addition to JSON/XML data structures in the Response Body, we aim to return HTTP Status Codes that make sense to web caches and developers. But how do you go about mapping different classes of errors onto appropriate HTTP Status codes? Everyone on the team agrees on the following: <blockquote> GET /package/1234 returns 404 Not Found if 1234 doesn't exist GET /package/1234/next_checkpoint returns 400 Bad Request if "next_checkpoint" and 1234 are valid to ask for but next_checkpont here doesn't make sense... </blockquote> and so on... but, in some cases, things needs to be more specific than just "400" - for example: <blockquote> POST /dispatch/?for_package=1234 returns 412 Precondition Failed if /dispatch and package 1234 both exist, BUT 1234 isn't ready for dispatch just yet. </blockquote> <hr> (Edit: <a href="http://tools.ietf.org/html/rfc2616#section-10" rel="noreferrer" title="RFC2616">Status codes in HTTP/1.1</a> and <a href="http://tools.ietf.org/html/rfc4918#section-11" rel="noreferrer" title="RFC4918">Status codes in WebDAV ext.</a>)
Tags
<web-services><rest><http-status-codes>
Title
REST: Mapping application errors to HTTP Status codes
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USconny
UserOwnerUserId
1. USconny
plurals
PostLinksPostIdRelatedPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
2. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostLinksRelatedPostIdPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
2. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
3. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
3. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POREST: Mapping application errors to HTTP Status codes
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 POREST: Mapping application errors to HTTP Status codes
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
3. VO
 singulars
 PostPostId
 POREST: Mapping application errors to HTTP Status codes
 UserUserId
 USGregoire
 VoteTypeVoteTypeId
 VTFavorite
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.