It is default for some, others do not do it. No browser speaks h2c nowadays.
I think reading bytes on a connection which is supposed to allow h2c traffic should be fine. Then one could argue if 24 bytes can always be expected... Since we no longer enabled h2c by default in a server, I expect it to be fine. //Stefan > Am 12.10.2015 um 11:12 schrieb Yann Ylavic <ylavic....@gmail.com>: > > That would be better, but still the doc says "This mode falls outside > the RFC 7540 but has become widely implemented as it is very > convenient for development and testing". > Is this something used by real world h2 clients? > > On Mon, Oct 12, 2015 at 11:09 AM, Stefan Eissing > <stefan.eiss...@greenbytes.de> wrote: >> I plan to change it to only happen for servers, where h2/h2c is among >> configured protocols. >> >>> Am 12.10.2015 um 11:07 schrieb Yann Ylavic <ylavic....@gmail.com>: >>> >>> On Sun, Oct 11, 2015 at 7:15 PM, Yann Ylavic <ylavic....@gmail.com> wrote: >>>> On Sun, Oct 11, 2015 at 7:11 PM, Stefan Eissing >>>> <stefan.eiss...@greenbytes.de> wrote: >>>>> Don't think so. But loading the module should do no harm, I think. And it >>>>> does now. >>>> >>>> Isn't configuring H2Direct on which harms? >>> >>> Didn't figure out "H2Direct on" was the default for non-TLS. >>> I don't think it's a good idea, beyond the NNTP case, the admin should >>> have to enable this by her/his own. >>
