Re: [Chicken-janitors] #1074: intarweb request parsing and Spiffy handling of said requests is inconsistent in case of improper request line URIs

[Chicken Trac]

#1074: intarweb request parsing and  Spiffy handling of said requests is
inconsistent in case of improper request line URIs
----------------------+-----------------------------------------------------
  Reporter:  RvdH     |       Owner:  sjamaan               
      Type:  defect   |      Status:  new                   
  Priority:  major    |   Milestone:  someday               
 Component:  unknown  |     Version:  4.8.x                 
Resolution:           |    Keywords:  bad-request connection
----------------------+-----------------------------------------------------

Comment(by RvdH):

 First of all, I think the server should always respond with a status code.
 Disconnecting is (as you mentioned as well) not really nice.

 W3C says (http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html) the
 following on 400 Bad Request:

 {{{
 The request could not be understood by the server due to malformed syntax.
 The client SHOULD NOT repeat the request without modifications.
 }}}

 If the URI is not a URI, you could say it is malformed syntax, so
 returning a 400 is probably correct.

 If you do not like the idea of returning a 400, you could instead return a
 500 (Internal Server Error) for every exception/error that appears during
 parsing.

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