Permalink
Browse files

Update changelog.

  • Loading branch information...
1 parent 7e18989 commit b1811ca7bbd1c706bc6e96d9c2d78b5e6ced812e @oscarh oscarh committed Jul 24, 2009
Showing with 25 additions and 9 deletions.
  1. +25 −9 CHANGELOG
View
@@ -1,30 +1,46 @@
+Version ?:
+* Fix for unexpected messages after request has been completed
+ * When the client process is trapping exits (which some eunit versions seem
+ to be doing by default) there would be {'EXIT', Pid, normal} messages left
+ after completing requests which came from the lhttpc_client process.
+ These are now avoided.
+
Version 1.2.1:
* Fix confusion of arguments in request/9 (introduced in 1.2.0)
Version 1.2.0:
* Add support for options
- * {connect_timeout, Milliseconds}: Aborts the connect phase after Milliseconds
- * {send_retry, N}: The client will retry sending the request N times if the connection is closed
+ * {connect_timeout, Milliseconds}: Aborts the connect phase after
+ Milliseconds
+ * {send_retry, N}: The client will retry sending the request N times
+ if the connection is closed
* Add support for downloading chunked transfer encoding
* More consistent error handling
- * The client can either return {ok, Result} or {error, Reason}. Reason wasn't very well defined before
- * connection_closed: The server closed the connection on us (N times in case it happens just after sending the request)
- * connect_timeout: If the TCP stack gives up or we hit the connect_timeout option
+ * The client can either return {ok, Result} or {error, Reason}. Reason
+ (which wasn't very well defined before) can now be:
+ * connection_closed: The server closed the connection on us (N times
+ in case it happens just after sending the request)
+ * connect_timeout: If the TCP stack gives up or we hit the
+ connect_timeout option
* timeout: If the overall request timeout value is hit
* All other errors (socket, protocol etc. will result in a runtime error)
* Better connection handling (issues #2 and #3 on bitbucket.org/etc/lhttpc)
* Now understands what to do with connections to servers < HTTP/1.1
* Now respects "Connection: close" in request headers, which means
clients can choose to not use persistent connections
* RFC Compliance
- * Fix reading of chunked encoding since section 3.6 claims that "All transfer-coding values are case-insensitive"
- * Support for responses that doesn't have an entity body (thanks to Steve Ellis)
- * No body for the HEAD and OPTIONS (unless indicated for the latter) methods
+ * Fix reading of chunked encoding since section 3.6 claims that "All
+ transfer-coding values are case-insensitive"
+ * Support for responses that doesn't have an entity body (thanks to Steve
+ Ellis)
+ * No body for the HEAD and OPTIONS (unless indicated for the latter)
+ methods
* Don't try to read a body when receiving a 204 status
Version 1.1.2:
* Fix minor error with {active, once} instead of {active, true} in manager
-* Remove socket and try to find another if the manager can't set controlling process due to socket error
+* Remove socket and try to find another if the manager can't set controlling
+ process due to socket error
* Improve test suite
Version 1.1.1:

0 comments on commit b1811ca

Please sign in to comment.