Yes I was under the false impression that Chrome did support h2c ; it does
not, as you pointed.
HTTP/2 works fine now.
Thanks
On Thu, Mar 30, 2017 at 10:46 PM, Mark Thomas wrote:
> On 30 March 2017 20:53:06 BST, Laurent Perez
> wrote:
> >Thank you Mark.
> >
> >h2c is enabled : 30-Mar-2017 21:3
On 30 March 2017 20:53:06 BST, Laurent Perez wrote:
>Thank you Mark.
>
>h2c is enabled : 30-Mar-2017 21:30:33.373 INFOS [main]
>org.apache.coyote.http11.AbstractHttp11Protocol.configureUpgradeProtocol
>The ["http-nio-8080"] connector has been configured to support HTTP
>upgrade
>to [h2c]
>
>Howeve
Am 30.03.2017 um 21:53 schrieb Laurent Perez:
> Client is Chrome 56. Where could I check in tomcat source to see if the
> client is sending the h2c upgrade token ?
>>> I managed to run the servlets/serverpush/simpleimage HTTP/2 push example
>>> from Tomcat 9 trunk with the SSL Http11AprProtocol c
Thank you Mark.
h2c is enabled : 30-Mar-2017 21:30:33.373 INFOS [main]
org.apache.coyote.http11.AbstractHttp11Protocol.configureUpgradeProtocol
The ["http-nio-8080"] connector has been configured to support HTTP upgrade
to [h2c]
However org.apache.catalina.connector.Request#newPushBuilder returns
On 30/03/17 18:02, Laurent Perez wrote:
> Hi
>
> I managed to run the servlets/serverpush/simpleimage HTTP/2 push example
> from Tomcat 9 trunk with the SSL Http11AprProtocol connnector and
> className="org.apache.coyote.http2.Http2Protocol"/>.
>
> Now I would like to enable HTTP/2 but without S
Hi
I managed to run the servlets/serverpush/simpleimage HTTP/2 push example
from Tomcat 9 trunk with the SSL Http11AprProtocol connnector and
.
Now I would like to enable HTTP/2 but without SSL : my certificates are
either hosted under my load balancer or Apache itself, and I do not require
SSL b