On 10/10/2015 12:20 AM, Stefan Eissing wrote:
In the meantime, I have prepped a howto h2 to point people to in order to
give/collect some advice. http://icing.github.io/mod_h2/howto.html
That will, once stable become part of the official docs.
Great, thanks! That is very helpful. One bit of feedback: in the Firefox
section you say that
> Among the response headers, you see this strange X-Firefox-Spdy entry
> listing "h2". That is the indication that HTTP/2 is used on this
> https: connection.
Another (possibly more future-proof?) indicator in that Network Headers
panel is the "Version: HTTP/2.0" field that is underneath the Status
Code and above the search bar.
Am 10.10.2015 um 02:24 schrieb Jacob Champion <[email protected]>:
(Haven't figured out the nghttp failure yet though.) Thanks Gregg!
For those following at home, and to save anyone else the trouble...
nghttp still wasn't working, so I
- built Wireshark trunk to get HTTP/2 dissection for the stream, but I
still couldn't decrypt the ephemeral ciphers, so I
- installed an LD_PRELOAD shim to get the pre-master secret keys only to
find that the encrypted alerts were simply disconnection notices, then
noticed that
- NPN was being sent in the Client Hello instead of ALPN, which is
probably because
- my nghttp is using my system OpenSSL (1.0.1) instead of my latest
compile (1.0.2).
The bleeding edge is fun. :)
In any case, I've now got an httpbin instance running in mod_passenger
over HTTP/2, which is very cool. I was originally hoping to help with
the vote, but now that I've discovered my binaries are mismatched, I
wouldn't trust my test results anyway. Maybe next time.
Good luck with the release!
--Jacob
