You are viewing a plain text version of this content. The canonical link for it is here.
Posted to bugs@httpd.apache.org by bu...@apache.org on 2015/12/17 09:51:41 UTC
[Bug 58745] New: H2Upgrade do not works
https://bz.apache.org/bugzilla/show_bug.cgi?id=58745
Bug ID: 58745
Summary: H2Upgrade do not works
Product: Apache httpd-2
Version: 2.5-HEAD
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: mod_http2
Assignee: bugs@httpd.apache.org
Reporter: bugzilla77@gmail.com
Add:
H2Upgrade off
to httpd.conf
Headers:
Upgrade: h2,h2c
Connection: Upgrade
are still sending.
According to the specifications they should not.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org
[Bug 58745] H2Upgrade do not works
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=58745
bugzilla77 <bu...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|2.5-HEAD |2.4.17
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org
[Bug 58745] H2Upgrade do not works
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=58745
Stefan Eissing <st...@eissing.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WONTFIX
Status|NEW |RESOLVED
--- Comment #1 from Stefan Eissing <st...@eissing.org> ---
The Upgrade: response header is calculated from your "Protocols" configuration.
The "H2Upgrade" setting is evaluated during an actual "Upgrade" requested by
the client.
Two different places in the server. It's unfortunate that you can configure the
server into such a state, but that is true for a lot of modules.
The way to solve your problem is to configure
Protocols http/1.1
in the server/vhost where you do not want to allow upgrades to HTTP/2. In case
you need help with this, please post your problem and configuration (apart from
the secret stuff) on the users mailing list.
Thanks.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org