I see Firefox using SPDY:
---------------------------------------
... no MAC keys used for this cipher
Client write key:
0000: 52 97 03 17 91 CF 7C 0A 55 2C A3 BB 02 06 DC E2 R.......U,......
Server write key:
0000: 96 4F F8 93 B1 6E 2F E9 A9 C0 D6 E6 8A 2C EB 43 .O...n/......,.C
Client write IV:
0000: 33 7D 19 F2 3...
Server write IV:
0000: 4F 04 BE E6 O...
Grizzly(2), READ: TLSv1.2 Change Cipher Spec, length = 1
Grizzly(2), READ: TLSv1.2 Handshake, length = 76
NPN selected protocol is: spdy/3.1
*** Finished
verify_data: { 123, 10, 117, 156, 81, 42, 155, 178, 196, 193, 249, 17 }
***
Grizzly(2), WRITE: TLSv1.2 Change Cipher Spec, length = 1
*** Finished
verify_data: { 168, 116, 13, 30, 179, 172, 120, 174, 66, 221, 18, 198 }
***
---------------------------------------
FF version: 43.0.4
As to HTTP/2, we plan to get back to work on HTTP/2 once I feel the
current issue list is in a good place. No ETA on when we expect to
complete the work, but it will be asap.
> Steve Curtis <mailto:stevo.curtis_at_googlemail.com>
> July 6, 2016 at 05:36
> 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.
>
>
> Ryan Lubke <mailto:ryan.lubke_at_oracle.com>
> July 5, 2016 at 11:55
> 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 <mailto:stevo.curtis_at_googlemail.com>
> July 5, 2016 at 03:21
> I've attached the output Ryan - hope this helps.
>
>
> Ryan Lubke <mailto: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
> <mailto:stevo.curtis_at_googlemail.com>> wrote:
>
> Steve Curtis <mailto: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
>
>