Forum Discussion
NimbostratusHTTP/2 only on client side
Hello Folks,
I've a question regarding to HTTP/2 on client side connections (HTTP/2 Profile (Server) -> none).
If I try to enable both "oneconnect" and "HTTP MRF Router" I get ...
Error bigip.f5.com mcpd[5774]: 01070734:3: Configuration error: Profile(s) found on /<partition>/<virtual server name> that are not allowed: Only (TCP Profile, ClientSSL Profile, ServerSSL Profile, HTTP Profile, HTTP2 Profile, HTTP Compression Profile, HTTP Router Profile) -> K81313105:
K81313105 -> disable "HTTP MRF Router".
Does it mean WebSocket traffic is possible again?
What I actually want to get at: What's the best practice for only HTTP/2 client-side connections? (HTTP/2 Profile (Client) -> http2)
1. oneconnect disabled and HTTP MRF Router enabled
2. oneconnect enabled and HTTP MRF Router disabled
3. both disabled
Thanks and BR
René
alven_kimAltostratus
Hello, rschwarz.
Oneconnect must not be used with HTTP/2.
Regards
rschwarzHello,
Yes I know. For Full-Proxy http2 on client and server side.
But what's the best way if http2 only activated on client side?
Thx
- Rodrigo_Albuque
Cirrocumulus
For HTTP/2 client side only option, the answer is 3: both disabled.
OneConnect is not compatible and HTTP MRF Router is supposed to be enabled when configuring HTTP/2 Full proxy.
Please check this out: https://techdocs.f5.com/en-us/bigip-15-1-0/big-ip-http2-full-proxy-configuration/http2-full-proxy-configuring.html#concept-1135
This is also mentioned in the article I wrote for AskF5: https://support.f5.com/csp/article/K04412053