On 3/28/2014 1:58 PM, Maxim Dounin wrote:
Nobody care enough to submit a patch.
Likely due to the fact that SNI isn't considered to be an option
for serious SSL-enabled sites anyway due to still limited
client-side support, see here for details:
Hello!
On Fri, Mar 28, 2014 at 02:53:18PM +, Jonathan Matthews wrote:
On 28 March 2014 14:31, Ben Johnson b...@indietorrent.org wrote:
Is there any way to av,oid this certificate being presented, but still
return the 444 response under the conditions I've described?
I'd /suspect/
On 3/28/2014 11:45 AM, Maxim Dounin wrote:
Hello!
On Fri, Mar 28, 2014 at 02:53:18PM +, Jonathan Matthews wrote:
On 28 March 2014 14:31, Ben Johnson b...@indietorrent.org wrote:
Is there any way to av,oid this certificate being presented, but still
return the 444 response under the
Jonathan Matthews Wrote:
---
bugs/features like this will get exponentially more attention after
Windows XP goes EOL this April, as (I believe) it's the last major
platform not to support SNI.
Which is a moot case since there are at least 5
Hello,
We run multiple vhosts in nginx. Occasionally, a vhost will be
mis-configured or disabled (via the website management software that we
use), and public requests for the domain will fall-back to nginx's
default vhost, which can have very unintended consequences (e.g., an
incorrect and
On 28 March 2014 16:51, Ben Johnson b...@indietorrent.org wrote:
Maxim, when you say, If SNI is used, it's in theory possible to close a
connection early, do you mean to imply that while possible, this
capability has not yet been implemented in nginx (the tickets are still
open after almost
On 28 March 2014 14:31, Ben Johnson b...@indietorrent.org wrote:
Is there any way to av,oid this certificate being presented, but still
return the 444 response under the conditions I've described?
I'd /suspect/ not, as the 444 response can't be delivered (i.e. the
connection closed) until
