HTTP/2 support | Community
Skip to main content
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 JustinEd3

Hi,

There's three separate elements here:

  1. Web server (where the actual clients get content)
  2. Dispatcher (the module in the web server which proxies requests to AEM)
  3. AEM's HTTP stack.

#1 is available today using mod_h2: https://github.com/icing/mod_h2 and will be in the next release of Apache HTTPD. This is also the most relevant issue.

#2 is dependent upon #3 as there's no point in the Dispatcher supporting HTTP/2 until it has something to access.

#3 requires an update to the Felix HTTP Jetty bundle. I created https://issues.apache.org/jira/browse/FELIX-5002 to track this if you want to watch that issue.

If #2 and #3 are important to you, I'd suggest filing a DayCare issue so this can be properly prioritized.

Regards,

Justin

2 replies

MarkJ_TX
MarkJ_TX
New Participant
December 13, 2016

Is there any update to this now?  Is http/2 fully supported by AEM now?

    J
    JustinEd3Accepted solution
    Employee
    October 16, 2015

    Hi,

    There's three separate elements here:

    1. Web server (where the actual clients get content)
    2. Dispatcher (the module in the web server which proxies requests to AEM)
    3. AEM's HTTP stack.

    #1 is available today using mod_h2: https://github.com/icing/mod_h2 and will be in the next release of Apache HTTPD. This is also the most relevant issue.

    #2 is dependent upon #3 as there's no point in the Dispatcher supporting HTTP/2 until it has something to access.

    #3 requires an update to the Felix HTTP Jetty bundle. I created https://issues.apache.org/jira/browse/FELIX-5002 to track this if you want to watch that issue.

    If #2 and #3 are important to you, I'd suggest filing a DayCare issue so this can be properly prioritized.

    Regards,

    Justin

    Terms & ConditionsAccessibility statement

    Loading footer...