When rfc8441 (extended connect) is disabled via
h2-workaround-bogus-websocket-clients, we properly refrain from
advertising support for extended connect, but we should also ignore
the incoming setting, otherwise it can remain enabled if the client
advertises it.
This should be backported to stable versions.
}
break;
case H2_SETTINGS_ENABLE_CONNECT_PROTOCOL:
- if (arg == 1)
+ /* setting only considered if rfc8441 not disabled */
+ if (arg == 1 && !(global.tune.options & GTUNE_DISABLE_H2_WEBSOCKET))
h2c->flags |= H2_CF_RCVD_RFC8441;
break;
}