Some weeks ago the backporting of the ALPN patch was rejected as a more generic approach was asked for.
Some hinted that an approach of defining a list of supported "Protocols" per server/vhost and a general registry for some callbacks where mod_ssl and mod_h2 would work with. This and the 421 return code on mismatching host names are the technical obstacles of backporting mod_h2 to 2.4, it seems. Does someone feel like implementing such a thing? Shall I take a stab at it? How should it best be approached? A separate core module which stores things at its own server config? It needs to fit into 2.4 somehow... Have a nice weekend, Stefan <green/>bytes GmbH Hafenweg 16, 48155 Münster, Germany Phone: +49 251 2807760. Amtsgericht Münster: HRB5782
