@Hostasaurus.Com
In essence, the custom template
should work like a charm, but actually
does NOT add value.
In fact, the custom template still allows HTTP/1 via requests that are based upon http:// URLs (note that this assumes that "https" protocol is not enforced by Nginx directives).
Another (more important) fact, Apache should be supporting HTTP/2 too, in order to make it worthwhile to have a HTTP/2 enabled Nginx.
Actually, running a HTTP/2 enabled Nginx with an Apache instance without HTTP/2 support can be (
very) dangerous: the power of Nginx (i.e. tenthousands of requests per second) is utilised to a higher degree with HTTP/2 (as a result of multiplexing) and can shutdown and even destroy Apache completely, certainly in the case of bad configuration of either Nginx or Apache, with respect to connections (and limits thereof), workers (and numbers thereof) and so on.
Moreover, a bad configuration of Nginx or Apache can result in requests effectively being served
as if the HTTP/1 protocol applies
, even though Nginx is HTTP/2 enabled.
The above is somewhat simplified, but you probably know what I am trying to say.
Regards....