On Wed, Apr 20, 2016 at 11:25 AM, Stefan Eissing <stefan.eiss...@greenbytes.de> wrote: > Done in r1740075. > > I was thinking of a nicer solution, but that involved inventing new hooks > which seems not worth it. > > Since this area of protocol negotiation has already been talked about in > regard to TLS upgrades > and websockets, I do not want to invest in the current way of handling this > too much time.
I really don't see why we couldn't upgrade to h2 from "http:" (not "https:" since ALPN did not take place already, or would have done it). ISTM that "Upgrade: h2" could be valid in response to a (plain) HTTP/1 request, and the client could upgrade from there... Regards, Yann. PS: feel free to ignore this message since that's already ruled :)
