From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-3.3 required=3.0 tests=ALL_TRUSTED,AWL,BAYES_00, RP_MATCHES_RCVD,URIBL_BLOCKED shortcircuit=no autolearn=unavailable version=3.3.2 X-Original-To: yahns-public@yhbt.net Received: from localhost (dcvr.yhbt.net [127.0.0.1]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPSA id 38A8B20469; Fri, 8 Apr 2016 20:01:35 +0000 (UTC) Date: Fri, 8 Apr 2016 20:01:34 +0000 From: Eric Wong To: ruby-talk@ruby-lang.org, yahns-public@yhbt.net Subject: [ANN] yahns 1.12.3 -_- sleepy app server for Ruby Message-ID: <20160408-yahns-1.12.3-unle@shed> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline List-Id: 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. Changes: yahns 1.12.3 - more fixes and doc updates This release only contains two changes since v1.12.2: * proxy_http_response: workaround non-terminated backends The first is a fix for the undocumented and unstable "proxy_pass" feature: https://yhbt.net/yahns-public/20160406062556.10988-1-e@80x24.org/t/ However, I'm considering supporting proxy_pass as a stable API: https://yhbt.net/yahns-public/20160220081619.GA10850@dcvr.yhbt.net/t/ * doc: recommend "verify_mode: OpenSSL::SSL::VERIFY_NONE" Only a documentation change prompted by the discovery that some browsers/platforms will try to prompt users for client certs: https://yhbt.net/yahns-public/20160316003434.GA14791@dcvr.yhbt.net/t/ 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. * git clone git://yhbt.net/yahns * http://yahns.yhbt.net/README * http://yahns.yhbt.net/NEWS.atom.xml * we only accept plain-text email yahns-public@yhbt.net * and archive all the mail we receive: http://yhbt.net/yahns-public/ * nntp://news.public-inbox.org/inbox.comp.lang.ruby.yahns