Thanks for the many answers!
Now, can I win someone over to propose backporting the mod_ssl ALPN changes? I
have prepared something:
* mod_ssl: add ALPN support by allowing other modules to register callbacks
for negotiation of the application layer protocol.
trunk patch: http://svn.apache.org/r1676709
http://svn.apache.org/r1676004
http://svn.apache.org/r1670578
http://svn.apache.org/r1675459
http://svn.apache.org/r1670436
http://svn.apache.org/r1670434
http://svn.apache.org/r1670397
http://svn.apache.org/r1332643
http://svn.apache.org/r1487772
http://svn.apache.org/r1332643
2.4.x patch:
https://raw.githubusercontent.com/icing/mod_h2/master/sandbox/httpd/patches/httpd-2.4.x-alpn.patch
I tested today’s httpd/branches/2.4.x + patch with mod_h2 on OS X, using
openssl 1.0.2. Works for me.
//Stefan
> Am 26.05.2015 um 11:07 schrieb Yann Ylavic <ylavic....@gmail.com>:
>
> Oups, several simultaneous responses...
> Hope too much information does not kill the information :p
>
> On Tue, May 26, 2015 at 11:03 AM, Yann Ylavic <ylavic....@gmail.com> wrote:
>> Hi Stefan,
>>
>> On Tue, May 26, 2015 at 10:37 AM, Stefan Eissing
>> <stefan.eiss...@greenbytes.de> wrote:
>>> Sorry, if this question has an obvious answer which I was unable to find:
>>> where would I find a list of the changes that will be backported to the
>>> 2.4.13 release in order to see if a change has received enough votes?
>>
>> Backports are proposed in the STATUS file of the target branch, where
>> each entry is removed once accepted and the backport is done.
>> There then only remains the CHANGES entry (if it was part of the
>> backport, but that's generally the case).
>>
>> But obviously, for a change to receive enough votes, it has first to
>> be proposed in STATUS...
>>
>> Regards,
>> Yann.
<green/>bytes GmbH
Hafenweg 16, 48155 Münster, Germany
Phone: +49 251 2807760. Amtsgericht Münster: HRB5782
