Do you also use HTTP/2 at the backend, between front door and the pools at the backend (our servers, setup for http/2) ? How do we set that up? If not, what’s the plan?
⚠Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
@SidShetye HTTP/2 is End to End, and is supported by default in all Azure Front Door configurations.
If your backend servers support HTTP/2, this should work with no additional configuration.
At https://docs.microsoft.com/th-th/azure/frontdoor/front-door-faq it says
How does Azure Front Door Service support HTTP/2?
HTTP/2 protocol support is available to clients connecting to Azure Front Door Service only. The communication to backends in the backend pool is over HTTP/1.1. HTTP/2 support is enabled by default.
That source is wrong?
@SidShetye that source is quite wrong, and that info should be in this document!
I have assigned the issue to the content author to evaluate and update as appropriate.
@TravisCragg-MSFT - @SidShetye is correct and that HTTP/2 is only supported from Client to AFD, but not AFD to the backend. Do you want to raise a PR for fixing this page to have that info as well?
@sharad4u I created #44349 to state the frontend HTTP/2 connectivity.
The confusion was caused by This Section of the overview document. Would you like me to create a PR to edit that section as well?
@sharad4u whats the plan for FD to backend going http/2?
@sharad4u @TravisCragg-MSFT what is the status on this one? Sounds like:
1) end-to-end HTTP/2 is now implemented in FD and this issue can be closed. (Yeah!!)
or
2) the documentation is still incorrect (or incomplete at best) and PR #44349 should be merged to publicly share limitations on HTTP/2 support.
Could this please be clarified, once and for all? Can AFD use HTTP/2 against backend servers?
Most helpful comment
@sharad4u whats the plan for FD to backend going http/2?