Release Name: 0.3.1

Notes:
kcar 0.3.1 - Kcar::Response minor bugfix

kcar features an HTTP parser that will convert a bytestream into a
3-element array suitable for use as a Rack response.  It is IO interface
agnostic, so it may be used with HTTP streams over Unix domain sockets,
regular files, FIFOs, StringIOs as well as traditional TCP sockets.

* http://bogomips.org/kcar/
* kcar@librelist.org
* git://bogomips.org/kcar.git
* http://bogomips.org/kcar/NEWS.atom.xml

Changes:

One bugfix for the optional Kcar::Response module:

* propagate EOFError on remote errors

  When proxying remote requests, EOFError may get incorrectly
  discarded when a the remote server sets the Content-Length:
  header _and_ Connection:close to disconnect the connection.

  We will now raise errors correctly when Connection:close
  is give but we have not yet read the expected Content-Length.



Changes:
 GIT-VERSION-GEN       |  2 +-
 lib/kcar/response.rb  | 14 ++++----------
 test/test_response.rb | 29 +++++++++++++++++++++++++++--
 3 files changed, 32 insertions(+), 13 deletions(-)

commit 7a51fde712fdbf40db080c30f91caf59a9dd9d7a
Author: Eric Wong 
Date:   Wed Sep 26 02:41:58 2012 +0000

    kcar 0.3.1 - Kcar::Response minor bugfix
    
    One bugfix for the optional Kcar::Response module:
    
    * propagate EOFError on remote errors
    
      When proxying remote requests, EOFError may get incorrectly
      discarded when a the remote server sets the Content-Length:
      header _and_ Connection:close to disconnect the connection.
    
      We will now raise errors correctly when Connection:close
      is give but we have not yet read the expected Content-Length.

commit a942f4f35af6d2764f05c3f76186b383142f7d3b
Author: Eric Wong 
Date:   Tue Sep 25 18:04:37 2012 -0700

    response: propagate EOFError on remote errors
    
    When proxying remote requests, EOFError may get incorrectly
    discarded when a the remote server sets the Content-Length:
    header _and_ Connection:close to disconnect the connection.
    
    We will now raise errors correctly when Connection:close
    is give but we have not yet read the expected Content-Length.