From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <normalperson@yhbt.net>
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=-2.7 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 B832220276; Mon, 15 Feb 2016
 06:00:36 +0000 (UTC)
Date: Mon, 15 Feb 2016 06:00:36 +0000
From: Eric Wong <normalperson@yhbt.net>
To: ruby-talk@ruby-lang.org, yahns-public@yhbt.net
Subject: Re: [ANN] yahns 1.12.0 -_- sleepy app server for Ruby
Message-ID: <20160215060036.GA32344@dcvr.yhbt.net>
References: <20160214-yahns-1.12.0-released@yhbt.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20160214-yahns-1.12.0-released@yhbt.net>
List-Id: <yahns-public@yhbt.net>

Eric Wong <normalperson@yhbt.net> wrote:
>           proxy_pass: pass X-Forwarded-Proto through

Note: proxy_pass is still broken with TLS because SSL_write
seems picky about getting EXACTLY the same args it got the
first time around when it got SSL_ERROR_WANT_{WRITE,READ}.

So it looks like packetized buffering is necessary for fast
upstreams and slow TLS clients.