Community
Participate
Working Groups
This is a follow on from Bug 374402. We did the investigation to enable SPDY and HTTP/2 on our Orion server but it has became apparent that they need to be enabled on the proxy because clients talk to the proxy and not the server directly. What proxy are we running for the orionhub.org and orion.eclipse.org servers?
(In reply to Anthony Hunter from comment #0) > This is a follow on from Bug 374402. > > We did the investigation to enable SPDY and HTTP/2 on our Orion server but > it has became apparent that they need to be enabled on the proxy because > clients talk to the proxy and not the server directly. > > What proxy are we running for the orionhub.org and orion.eclipse.org servers? Ok, you are using Apache/2.4.6 (Linux/SUSE) How do you feel about adding a mod_spdy module? https://github.com/eousphoros/mod-spdy There is not an HTTP/2 module for Apache yet.
"Throughout the process, the core developers of SPDY have been involved in the development of HTTP/2, including both Mike Belshe and Roberto Peon. As of February 2015, Google has announced that following the recent final ratification of the HTTP/2 standard, support for SPDY would be deprecated, and that support for SPDY will be withdrawn completely in 2016." http://blog.chromium.org/2015/02/hello-http2-goodbye-spdy-http-is_9.html
I'd rather just wait for HTTP/2 support for Apache.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
(In reply to Denis Roy from comment #3) > I'd rather just wait for HTTP/2 support for Apache. We have begun using HTTP/2 at our edge gateway, so enabling it for each site should happen automatically over time.
