Forum Discussion
4 Replies
- R_MarcNimbostratus
Timely question. I just created a production HTTP/2 enabled site. I added it to several staging sites as well. I haven't seen any ill effects, and my testing of the actual HTTP/2 stuff seems to work just fine (note, the back end need not speak http/2...at least that's my experience).
R Marc,
thanks for the quick response. Would you mind sharing how you configured it?
/Riad
- R_MarcNimbostratus
It was pretty simple. You don't have to do it this way, but it's I think it's cleaner this way:
Create a new http2 profile:
create ltm profile http2 some-name-http2-profile { }
Then just attach that to your existing http enabled service (note that client SSL is a requirement for http/2):
modify ltm virtual some-name-http-virtual { profiles add { some-name-http2-profile }}
You could do this in the GUI too, but who wants to do that?
To test you'll need a http/2 enabled client. Most recent browsers support it, but I couldn't see any way to validate using a browser, so I used nghttp2 to test it (https://github.com/tatsuhiro-t/nghttp2). It's nice as a validation as it doesn't support http/1.0 or 1.1.
Thank you Marc! This really helps us.
/Riad