Does the Day Commons HTTP Client support HTTP2? | Community
Skip to main content
roberth10066577
roberth10066577
Level 2
March 20, 2019
Solved

Does the Day Commons HTTP Client support HTTP2?

  • March 20, 2019
  • 2 replies
  • 1158 views

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?

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by joerghoh

    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

    2 replies

    Gaurav-Behl
    Gaurav-Behl
    Level 10
    March 20, 2019

    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 to an HTTP/1.1 only s… 

    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-use.html

    Adobe Experience Manager Help | Using the SSL Wizard in AEM

    List of browsers-versions that support HTTP2

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

      joerghoh
      Adobe Employee
      joerghohAdobe EmployeeAccepted solution
      Adobe Employee
      March 20, 2019

      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

        Terms & ConditionsAccessibility statement

        Loading footer...