I noticed that myself Ryan, and have been testing the development with
FireFox using the "HTTP/2 and SPDY indicator" extension.
I guess you have no roadmap for HTTP2 support in Grizzly anytime soon?
Is there any chance you could repeat your test using FireFox? I think I
may end up going down the HTTP2 enabled proxy route here, but I'd like to
finish this investigation regardless, since I'm still not clear why this
would;t be working via FireFox/IE.
On 5 July 2016 at 19:55, Ryan Lubke <ryan.lubke_at_oracle.com> wrote:
> Okay, so I think the root of the issue is detailed in this blog post [1].
>
> When I tested using Chromium on Ubuntu, NPN and SPDY were still supported
> and it worked. But testing with Chrome (version 51), The client, over
> ALPN, only supports HTTP/1.1 and HTTP/2.
>
> Grizzly's HTTP/2 support is still in development, and this information is
> a good reason to put more time into it.
>
> [1] http://blog.chromium.org/2016/02/transitioning-from-spdy-to-http2.html
>
> Steve Curtis <stevo.curtis_at_googlemail.com>
> July 5, 2016 at 03:21
> I've attached the output Ryan - hope this helps.
>
>
> Ryan Lubke <ryan.lubke_at_oracle.com>
> July 4, 2016 at 11:51
> Yes, I was able to. Can you send me your SSL handshake log?
>
> Sent from my iPhone
>
> On Jul 4, 2016, at 03:21, Steve Curtis <stevo.curtis_at_googlemail.com>
> wrote:
>
> Steve Curtis <stevo.curtis_at_googlemail.com>
> July 4, 2016 at 03:21
> Hi Ryan,
>
> Thanks for the suggestions. I made the code changes (see Travis CI
> https://travis-ci.org/stevocurtis/public-development/builds/142066549 for
> build output).
>
> The code builds fine and I ran it up with Open JDK 8.0.92 but it still
> doesn't seem to be using the SPDY protocol, note I'm using FireFox HTTP/2
> and SPDY indicator addon to test this.
>
> Have you been able to run this up and test this locally? Or is there an
> example SPDY enabled app I could use as a reference?
>
> At this point I'm tempted to rule this out as not working and look at
> putting a HTTP2 enabled proxy in front of my appserver instead.
>
> Steve
>
>
> Ryan Lubke <ryan.lubke_at_oracle.com>
> June 27, 2016 at 14:34
> Hi Steve,
>
> Sorry for the delay.
>
> There's a minor change in JerseyGrizzlyFrameworkServer that should get
> your further. Line 48, change to:
>
> server = GrizzlyHttpServerFactory.createHttpServer(uri, resourceConfig,
> true, createSSLContextConfigurator(), false);
>
> Note, JDK 1.7 probably won't work with our NPN implementation due to
> changes for SNI. Grizzly NPN 1.2 was released for OpenJDK 1.8.0_25.
> It most definitely won't work with the latest OpenJDK 1.8 release
> (1.8.0_92). I've updated the NPN/ALPN implementation to work with this
> version and will be releasing later today.
>
> At any rate, let's see where the aforementioned code change gets you and
> go from there.
>
> Thanks,
> -rl
>
>
> Steve Curtis <stevo.curtis_at_googlemail.com>
> June 16, 2016 at 02:56
> Thanks Ryan - appreciate it.
>
> I've tried to make it as easy as possible to replicate, the github project
> is simple maven build and you can run the server up either
> via JerseyGrizzlyFrameworkServer (has a main method) or
> the JerseyGrizzlyFrameworkServerTest unit test.
>
> I'm convinced it is something very obvious I've missed :-)
>
> Cheers
>
>
>
>