[Bug 59311] Do not send "Upgrade: h2" header to HTTP/1.1 clients when SSL/TLS is used

https://bz.apache.org/bugzilla/show_bug.cgi?id=59311 --- Comment #11 from Mark Nottingham --- This is a seriously weird issue. No other implementation uses Upgrade AFAICT, and it's now explicitly deprecated in 7540bis as a result. Yes, Apache is free to send 'upgrade' if it's willing to do so,

[Bug 59311] Do not send "Upgrade: h2" header to HTTP/1.1 clients when SSL/TLS is used

https://bz.apache.org/bugzilla/show_bug.cgi?id=59311 Christophe JAILLET changed: What|Removed |Added URL|https://www.pcloudy.com | -- You are receiving this mail

[Bug 59311] Do not send "Upgrade: h2" header to HTTP/1.1 clients when SSL/TLS is used

https://bz.apache.org/bugzilla/show_bug.cgi?id=59311 incs...@gmail.com changed: What|Removed |Added URL||https://www.pcloudy.com -- You

[Bug 59311] Do not send "Upgrade: h2" header to HTTP/1.1 clients when SSL/TLS is used

https://bz.apache.org/bugzilla/show_bug.cgi?id=59311 Paul Menzel changed: What|Removed |Added CC||pmenzel+bz.apache.org@molge

[Bug 59311] Do not send "Upgrade: h2" header to HTTP/1.1 clients when SSL/TLS is used

https://bz.apache.org/bugzilla/show_bug.cgi?id=59311 bamb...@vshosting.cz changed: What|Removed |Added CC||bamb...@vshosting.cz -- You

[Bug 59311] Do not send "Upgrade: h2" header to HTTP/1.1 clients when SSL/TLS is used

https://bz.apache.org/bugzilla/show_bug.cgi?id=59311 Szőgyényi Gábor changed: What|Removed |Added CC|

[Bug 59311] Do not send "Upgrade: h2" header to HTTP/1.1 clients when SSL/TLS is used

https://bz.apache.org/bugzilla/show_bug.cgi?id=59311 brian russell changed: What|Removed |Added CC|

[Bug 59311] Do not send "Upgrade: h2" header to HTTP/1.1 clients when SSL/TLS is used

https://bz.apache.org/bugzilla/show_bug.cgi?id=59311 --- Comment #10 from Michael Kaufmann --- > As per dev discussion on the list, we'd like to fix this (by default without > further config) for the UAs that have problems with it. I asked you for the > UA

[Bug 59311] Do not send "Upgrade: h2" header to HTTP/1.1 clients when SSL/TLS is used

https://bz.apache.org/bugzilla/show_bug.cgi?id=59311 --- Comment #9 from Stefan Eissing --- Michael, it is nice that you reference my mail. It would be even more helpful if you could answer the question I asked you: As per dev discussion on the list, we'd like to fix this

[Bug 59311] Do not send "Upgrade: h2" header to HTTP/1.1 clients when SSL/TLS is used

https://bz.apache.org/bugzilla/show_bug.cgi?id=59311 Michael Kaufmann changed: What|Removed |Added Resolution|FIXED

[Bug 59311] Do not send "Upgrade: h2" header to HTTP/1.1 clients when SSL/TLS is used

https://bz.apache.org/bugzilla/show_bug.cgi?id=59311 Jim Jagielski changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 59311] Do not send "Upgrade: h2" header to HTTP/1.1 clients when SSL/TLS is used

https://bz.apache.org/bugzilla/show_bug.cgi?id=59311 --- Comment #7 from Laurence 'GreenReaper' Parry --- One other thing this breaks: nginx cached responses. This caused us to rollback our Apache HTTP/2 upgrade because iOS Safari clients were unable to load files from

Re: [Bug 59311] Do not send "Upgrade: h2" header to HTTP/1.1 clients when SSL/TLS is used

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, wrote: >

[Bug 59311] Do not send "Upgrade: h2" header to HTTP/1.1 clients when SSL/TLS is used

https://bz.apache.org/bugzilla/show_bug.cgi?id=59311 --- Comment #6 from Stefan Eissing --- 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

[Bug 59311] Do not send "Upgrade: h2" header to HTTP/1.1 clients when SSL/TLS is used

https://bz.apache.org/bugzilla/show_bug.cgi?id=59311 --- Comment #5 from Michael Kaufmann --- I don't need a workaround, I can compile Apache from the sources and apply r1740075 + r1740119 ;-) I think a good solution would be that the setting "H2Upgrade

[Bug 59311] Do not send "Upgrade: h2" header to HTTP/1.1 clients when SSL/TLS is used

https://bz.apache.org/bugzilla/show_bug.cgi?id=59311 Stefan Eissing changed: What|Removed |Added Keywords|FixedInTrunk, |TryAgain

[Bug 59311] Do not send "Upgrade: h2" header to HTTP/1.1 clients when SSL/TLS is used

https://bz.apache.org/bugzilla/show_bug.cgi?id=59311 Michael Kaufmann changed: What|Removed |Added Keywords|

[Bug 59311] Do not send "Upgrade: h2" header to HTTP/1.1 clients when SSL/TLS is used

https://bz.apache.org/bugzilla/show_bug.cgi?id=59311 --- Comment #2 from Michael Kaufmann --- >From RFC 7540 (HTTP/2), section 3.2: > A server MUST ignore an "h2" token in an Upgrade header field. Presence of a > token with "h2" implies HTTP/2 over TLS,

[Bug 59311] Do not send "Upgrade: h2" header to HTTP/1.1 clients when SSL/TLS is used

https://bz.apache.org/bugzilla/show_bug.cgi?id=59311 Michael Kaufmann changed: What|Removed |Added Keywords|

[Bug 59311] Do not send "Upgrade: h2" header to HTTP/1.1 clients when SSL/TLS is used

https://bz.apache.org/bugzilla/show_bug.cgi?id=59311 --- Comment #1 from Michael Kaufmann --- Created attachment 33755 --> https://bz.apache.org/bugzilla/attachment.cgi?id=33755=edit Proposed patch: Do not send "Upgrade: h2" -- You are receiving this mail