The correct fix, in this particular case, is to use the Header unset mechanism, for the specific user-agent only.
What is the User-agent string of the offended client application? On Thu, Jun 16, 2016 at 3:12 AM, <[email protected]> wrote: > https://bz.apache.org/bugzilla/show_bug.cgi?id=59311 > > --- Comment #6 from Stefan Eissing <[email protected]> --- > It's not really HTTP/2 specific, although that is where you currently > observer > it. So, a better directive would be placed in core, such as > > ProtocolsHttpUpgradeAnnounce on|off > > to suppress a response header and > > ProtocolsHttpUpgrade on|off > > to disable the whole mechanism (including announce). > > -- > You are receiving this mail because: > You are the assignee for the bug. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
