I agree with your analysis, "h2" is not an upgrade candidate. "h2c" is an upgrade candidate.
This isn't even an HTTP/2 issue (unless the working group reverses themselves on accepting Upgrade: h2 protocol switching), until we accept Upgrade: h2 we should be dropping h2 from the server Upgrade: response header. But do let us know what the wg feedback is. On Tue, Apr 19, 2016 at 7:47 AM, Michael Kaufmann <m...@michael-kaufmann.ch> wrote: > Hi, > > you may already know that HTTP/2 clients use ALPN to advertise support for > HTTP/2 when TLS is used. > > The issue is this: When mod_http2 is enabled, Apache sends an "Upgrade: > h2" response header to clients that have *not* advertised support for > HTTP/2 (clients that speak only HTTP/1.x). > > I think that this is wrong, because of this sentence in RFC 7540: > >> A server MUST ignore an "h2" token in an Upgrade header field. Presence >> of a token with "h2" implies HTTP/2 over TLS, which is instead negotiated >> as described in Section 3.3. >> > > What do you think about this issue, and what do you think about the > attached patch in bug 59311? > > Regards, > Michael > >
