I've noticed this happening more and more often...
http://httpd.markmail.org/search/?q=+list%3Aorg.apache.httpd.cvs+%22vote+discarded%22
Here's one arbitrary example - there are many committers implicated here...
--- httpd/httpd/branches/2.4.x/STATUS (original) +++
httpd/httpd/branches/2.4.x/ST
Due to some possible last-minute changes, I am REVOKING
this VOTE.
On Thu, Jun 4, 2015 at 11:33 AM, Jim Jagielski wrote:
> The pre-release test tarballs for Apache httpd 2.4.13 can be found
> at the usual place:
>
> http://httpd.apache.org/dev/dist/
>
> I'm calling a VOTE on releasing these as Apache httpd 2.4.13 GA.
>
> [X] -1: Danger Will Robinson. And
> On Jun 4, 2015, at 12:33 PM, Jim Jagielski wrote:
>
> The pre-release test tarballs for Apache httpd 2.4.13 can be found
> at the usual place:
>
> http://httpd.apache.org/dev/dist/
>
> I'm calling a VOTE on releasing these as Apache httpd 2.4.13 GA.
>
> [X] +1: Good to go
Fed 20, x86
>
> What's the point of SNI if it can be used to select the correct vhost
> before the handshake (modulo the port...), but TLS must possibly be
> renegotiated later for subsequent requests?
>
In configs that use separate certificates, it gets you the correct one, and
these are n/a to the coalescin
It was raised by Stefan Eissing in [1] that HTTP/2 (not surprisingly)
encourages UA/clients to reuse established connections even for
differents hostnames, provided they "resolve to the same IP address
and wildcard certs or matching alternate names in the certificate to
match".
This obviously is n
