Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-10064

Notify that HTTP/2 won't work due missing ALPN when having HTTP/2 enabled

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.1.0.DR17
    • 7.1.0.DR13, 7.1.0.DR15
    • Undertow
    • Hide

      Start EAP in default configuration/provided configuration (which doesn't use elytron) on IBM 1.8.0 => ./standalone.sh -c standalone-web.xml
      access with client supporting HTTP/2 https://localhost:8443/ and check what protocol version was used, you will notice that HTTP/1.1 is used when running on IBM 1.8 and there is no logged warning why HTTP/1.1 was used, when running on Oracle JDK or Open JDK, there will be HTTP/2 thanks to Undertow ALPN hack.

      Show
      Start EAP in default configuration/provided configuration (which doesn't use elytron) on IBM 1.8.0 => ./standalone.sh -c standalone-web.xml access with client supporting HTTP/2 https://localhost:8443/ and check what protocol version was used, you will notice that HTTP/1.1 is used when running on IBM 1.8 and there is no logged warning why HTTP/1.1 was used, when running on Oracle JDK or Open JDK, there will be HTTP/2 thanks to Undertow ALPN hack.

      There should be some log message notifying that ALPN is missing on given platform, informing user that even though he has enable-http2=true on https listener, and doing request from client supporting HTTP/2 it fails to use HTTP/2 and HTTP/1.1 is used instead.

      I believe there should be at least some warning log message when starting EAP with eanble-http2 on https listener with missing ALPN provider.

        1. standalone-web.xml
          7 kB

              sdouglas1@redhat.com Stuart Douglas (Inactive)
              rhatlapa@redhat.com Radim Hatlapatka (Inactive)
              Jan Stourac Jan Stourac
              Jan Stourac Jan Stourac
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: