Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Our first pass at assigning response codes to conditions used only standard codes. However, in some cases this stretched or even ignore the original purpose for the codes in question. Thus, we are switching to a better scheme as time permits.


HTTP Standard Codes

RFC2295, RFC2324, RFC2616, RFC2518, RFC2774, RFC2817, RFC3229, RFC3648, RFC4918

http://www.iana.org/assignments/http-status-codes


Below is a table of the codes currently specified by RFCs and the registry.

 

1xx

10x 12x

Informational

2xx

20x 22x

Successful

3xx

30x

Redirection

4xx

40x 41x 42x 44x 490x 49x

Client Error

5xx

50x 51x

Server Error

 



Blink HTTP Response Codes

Given the above ranges of official and semi-official codes, our Server Errors will start in the range 56x and our Client Errors will start in the range 46x. Unless it is clear that our usage is standards-compliant, we will avoid reusing existing codes.


BlinkForms2 Submission errors will start in the 47x range for Client Errors and 57x range for Server Errors


Below is a table of the codes that will be used by Blink’s internal AJAX services.

 

200

OK; body = content

204

No Content; no body

The request was successful but there is no data to be returned.

304

Not Modified; no body

The requested resource has not been modified since it was last requested.

400

Bad Request; body = description of request syntax error

The client should not repeat the request without modification.

464

Not Found; body = description of missing item

The item specified in the request could not be found.

470

Form Failed Validation; body = JSON

{ “errors”: { “field”: “error on field”, ... }, “message”: “display text” }

The form record submitted does not pass validation.

471

Form Custom Error; body = JSON

{ “errors”: { “field”: “error on field”, ... }, “message”: “display text” }

The form record submitted does not pass validation by the third-party service.

500

Internal Server Error; body = description of server error

An unexpected condition prevents the request from being fulfilled.

563

Illegal Interaction; body = description of server error

Selected Interaction contains unsafe or restricted code.

570

Service Not Found; body = …

The third-party service could not be successfully contacted.

  • No labels