On Tue, Dec 8, 2015 at 8:34 AM, Stefan Eissing <[email protected] > wrote:
> +1 for deferring any upgrade changes that do not fix real issues - like > the one proposed for backport by Bill - to 2.4.19 > Agreed, as spelled out in my top-post, simplest path to 2.4.18, and these interesting discussions over the past day point to no single simple path. Note that the pre-patch behavior caused tls to overwrite h2c, now the protocol API will overwrite tls upgrade advertisements on the first trip through. Does it make sense to @bug the new Protocol API's stating that these remain experimental and still subject to change, and refer prospective developer/consumers to dev@httpd? It seems something will change in a later 2.4 release, and its simply a matter of what is the appropriate straight path that can satisfy all of the prospective upgrade consumers.
