[infinispan-issues] [JBoss JIRA] (ISPN-8896) HTTP/2 support is broken

[Sebastian Łaskawiec (JIRA)]

Sebastian Łaskawiec created ISPN-8896:
-----------------------------------------

             Summary: HTTP/2 support is broken
                 Key: ISPN-8896
                 URL: https://issues.jboss.org/browse/ISPN-8896
             Project: Infinispan
          Issue Type: Bug
          Components: REST
    Affects Versions: 9.2.0.Final
            Reporter: Sebastian Łaskawiec


CURL reports that HTTP Settings frame is broken:

On Terminal 1:
{code}
docker run -e "APP_USER=test" -e "APP_PASS=test" jboss/infinispan-server:9.2.0.Final ../../docs/examples/configs/standalone-rest-ssl.xml
{code}

On Terminal 2:
{code}
curl "Accept: text/plain" -k -v --http2 -u test:test https://172.17.0.2:8443/rest/default/test      
* Illegal port number
* Closing connection -1
curl: (3) Illegal port number
*   Trying 172.17.0.2...
* TCP_NODELAY set
* Connected to 172.17.0.2 (172.17.0.2) port 8443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* skipping SSL peer certificate verification
* ALPN, server accepted to use h2
* SSL connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
* Server certificate:
* 	subject: CN=localhost
* 	start date: Mar 01 12:02:32 2018 GMT
* 	expire date: Feb 27 12:02:32 2028 GMT
* 	common name: localhost
* 	issuer: CN=localhost
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Server auth using Basic with user 'test'
* Using Stream ID: 1 (easy handle 0x55972b0700d0)
> GET /rest/default/test HTTP/2
> Host: 172.17.0.2:8443
> Authorization: Basic dGVzdDp0ZXN0
> User-Agent: curl/7.53.1
> Accept: */*
> 
* http2 error: Remote peer returned unexpected data while we expected SETTINGS frame.  Perhaps, peer does not support HTTP/2 properly.
* Closing connection 0
curl: (16) Illegal port number
{code}

The same with 9.1.5.Final:
{code}
curl -d test -H "Accept: text/plain" -k -v --http2 -u test:test https://172.17.0.2:8443/rest/default/test
*   Trying 172.17.0.2...
* TCP_NODELAY set
* Connected to 172.17.0.2 (172.17.0.2) port 8443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* skipping SSL peer certificate verification
* ALPN, server accepted to use h2
* SSL connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
* Server certificate:
* 	subject: CN=localhost
* 	start date: Mar 01 12:04:47 2018 GMT
* 	expire date: Feb 27 12:04:47 2028 GMT
* 	common name: localhost
* 	issuer: CN=localhost
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Server auth using Basic with user 'test'
* Using Stream ID: 1 (easy handle 0x555cd62630d0)
> POST /rest/default/test HTTP/2
> Host: 172.17.0.2:8443
> Authorization: Basic dGVzdDp0ZXN0
> User-Agent: curl/7.53.1
> Accept: text/plain
> Content-Length: 4
> Content-Type: application/x-www-form-urlencoded
> 
* We are completely uploaded and fine
* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
< HTTP/2 200 
< etag: application/x-www-form-urlencoded-235262424
< content-type: text/plain
< content-length: 0
< 
* Connection #0 to host 172.17.0.2 left intact
{code}



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)