Re: [Chicken-janitors] #1069: [intarweb] [PATCH] Full list of HTTP status codes

[Chicken Trac]

#1069: [intarweb] [PATCH] Full list of HTTP status codes
--------------------------+-------------------------------------------------
  Reporter:  RvdH         |       Owner:  sjamaan 
      Type:  enhancement  |      Status:  closed  
  Priority:  minor        |   Milestone:  someday 
 Component:  unknown      |     Version:  4.8.x   
Resolution:  fixed        |    Keywords:  intarweb
--------------------------+-------------------------------------------------

Comment(by RvdH):

 Thanks!

 I think most HTTP statuses are actually quite useful, they are just hardly
 used. :) Most often because developers do not know in what situations they
 should use them. Just returning a 403 or 404 in many cases, doesn't make
 it right. ;)

 e.g.

 We use 422 Unprocessable Entity a lot when the request is syntactically
 correct, but semantically not. For example, in form fields when an email
 address is required, but a regular string is entered, you can return a
 422.

 429 is often useful if you have a web service with a rate limit. Often
 done based on IP address: the free version is rate limited, while the paid
 version is not.

 I think in general an HTTP server should support all ''valid'' HTTP status
 codes. It is up to the application developers to choose the right ones.

-- 
Ticket URL: <http://bugs.call-cc.org/ticket/1069#comment:3>
Chicken Scheme <http://www.call-with-current-continuation.org/>
Chicken Scheme is a compiler for the Scheme programming language.