[ANN] yahns 1.14.1 -_- sleepy app server for Ruby

[Eric Wong <e@80x24.org>]

A Free Software, multi-threaded, non-blocking network
application server designed for low _idle_ power consumption.
It is primarily optimized for applications with occasional users
which see little or no traffic.  yahns currently hosts Rack/HTTP
applications, but may eventually support other application
types.  Unlike some existing servers, yahns is extremely
sensitive to fatal bugs in the applications it hosts.

* git clone git://yhbt.net/yahns
* https://yhbt.net/yahns/README
* https://yhbt.net/yahns/NEWS.atom.xml (supported by most "RSS" readers)
* we only accept plain-text email yahns-public@yhbt.net
* and archive all the mail we receive: https://yhbt.net/yahns-public/
* nntp://news.public-inbox.org/inbox.comp.lang.ruby.yahns

lrg nabgure ubeevoyl-anzrq freire :>

Changes:

    yahns 1.14.1 - bugfixes only

    This release avoids confusing HTTP/1.1 clients with a
    "Transfer-Encoding: chunked" header on bodyless responses.
    The header was causing "curl -T" to wait indefinitely for
    a response body after the server sent a 204.
    This regression was introduced with autochunk introduced
    with yahns 1.13(*).

    rack.hijack was also broken for ancient "HTTP/0.9" requests,
    and now fixed.

    4 changes since 1.14.0:

          queue_*: fix outdated comments
          http_response: support rack.hijack on HTTP/0.9 responses
          response: do not set chunked header on bodyless responses
          proxy_pass: do not chunk on bodyless upstream responses

    (*) https://yhbt.net/yahns-public/20160805-yahns-1.13.0-released@lucky13/

Please note the disclaimer:

  yahns is extremely sensitive to fatal bugs in the apps it hosts.  There
  is no (and never will be) any built-in "watchdog"-type feature to kill
  stuck processes/threads.  Each yahns process may be handling thousands
  of clients; unexpectedly killing the process will abort _all_ of those
  connections.  Lives may be lost!

  yahns hackers are not responsible for your application/library bugs.
  Use an application server which is tolerant of buggy applications
  if you cannot be bothered to fix all your fatal bugs.

-- 
EW