And does anyone know which version, draft or official, of HTTP2 the LTM in v12.0.0 supports?
I have a test server in v11.6.0 and HTTP2 no longer works with the latest versions of the major browsers.
Version 12.0 supports the final HTTP2 spec. 11.6.0 suports draft 14.
Because of the intertwining of http2 with SSL, it's unfortunately not as simple as merely dropping a http2 profile on the VIP. It has to be SSL-enabled, and needs to prefer certain ciphers that the http2 spec wants so that handshakes can complete successfully.
I know that you need at least this cipher string "ECDHE+AES-GCM:DEFAULT", but I haven't spent much time to test all the configuration options needed.
Hopefully this puts you in the right direction and someone else could add on it.
11.6.0 is marked as experimental and will remain so through all 11.6.x versions. The HTTP2 profile on 11.6.0 is definitely buggy - but it is clearly labelled as experimental as you've observed.
The problems I observed in 11.6.0 were typically resolved in 12.0.0. If you want to run HTTP/2 in production, use 12.0.0 (currently at hotfix 1).
The implementation should follow the RFC. However, one would still expect to see bugs, since draft/RFC difference are still being ironed out apparently! For example: https://support.f5.com/kb/en-us/solutions/public/17000/000/sol17023
I have tickets where key fixes to make APM work fully with HTTP/2 are missing.
HTTP/2 support is not really ready in APM for version 12.1, and the fixes were still "under consideration" according to support.
Ticket was opened April, so not really very impressed with F5 commitment to HTTP/2.
We'll likely look to use open source proxy and authentication components in place of F5 going forward.
Do you have any bugids?
ID600872 which is supposed to be fixed recetly I believe.
Support were uncertain if this would fix the issues with detecting activity in the Access Profile, but that looked like the same issue to me.
I have found that v11.6.0 no longer works with the current version of Firefox (v44.0.1) which supports the final http2 spec only and not http2draft: the config network.http.spdy.enabled.http2draft no longer exists in this browser.