Does the Day Commons HTTP Client support HTTP2?

[roberth10066577]

I know that apache 2.4.17+ can serve AEM hosted content using HTTP2 and the dispatcher module is agnostic to the HTTP version but does the day commons http client bundle support HTTP2 connections to external services e.g. web services where AEM is the client? More importantly, if the dispatcher apache server only allows HTTP2, will replication flush agents still be able to connect via HTTP2 to flush the dispatcher cache?

[Gaurav-Behl]

Per my knowledge, you would need to configure proxy (to make TLS v1.2 mandatory) for HTTP Client under '/system/console/configMgr' and get what you want to do.Depending on how you configure HTTP2 (strict or lenient) for both AEM and Dispatcher/Webserver, replication/flush agents would work otherwise throw error during connection establishment.

check if this helps -

http2 - What if an HTTP/1.1 client talk to an HTTP/2 only server and what if an HTTP/2 client talk t... 

https://daniel.haxx.se/http2/http2-v1.9.pdf

HTTP/2 - Wikipedia -

HTTP/2 is defined both for HTTP URIs (i.e. without encryption) and for HTTPS URIs (over TLS using ALPN extension^[30] where TLS 1.2 or newer is required).^[31]​ Although the standard itself does not require usage of encryption,^[32] all major client implementations (Firefox,^[33] Chrome, Safari, Opera, IE, Edge) have stated that they will only support HTTP/2 over TLS, which makes encryption de facto mandatory.^[34]

Day Commons HTTP Client configuration under /system/console/configMgr -

You could enable AEM on SSL per your use case:

SSL By Default https://helpx.adobe.com/experience-manager/kt/platform-repository/using/ssl-wizard-technical-video-u...

Adobe Experience Manager Help | Using the SSL Wizard in AEM

List of browsers-versions that support HTTP2

https://caniuse.com/#search=HTTP2

[Jörg_Hoh · Accepted solution]

You typically do not force the webserver to only accept HTTP/2, but it should always fallback to HTTP/1.1 if /2 is not supported by the requester.

Thus if your only concern is if enabling HTTP/2 support on the webservers will break dispatcher invalidation: It won't.

Jörg