Forum Discussion
F5 AWAF with HTTP/2, MRF and Websocket profiles
Thank you for the response. This helps a ton. Strange however, that F5 documentation states HTTP/2 requires MRF. Confusing. Thanks again.
considering that server side http/2 makes oneconnect unusable,
i'd rather have http/1.1 on server side.
in live traffic, the simultaneous loading features of http/2 is usually useful to load mutiple static contents (js, css and images).
meanwhile dynamic contents (login transaction, load user profile, etc.) mostly still happens sequentially.
hence, if caching static contents is enabled in ltm vserver,
then f5 barely needs to send simultaneous requests from a client session.
there are multiple dynamic content load from multiple client sessions in which oneconnect does tcp multiplexing
f5 and servers also connect via datacenter wired lan, so transport latency is under 1ms.
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com