Hi, On Tue, Sep 6, 2016 at 7:37 AM, John Jiang <john.sha.ji...@gmail.com> wrote: > I'm using Jetty 9.3.8, and made it supporting h2 and h2c, like the below > info on starting the server. > 2016-09-06 13:23:52.505:INFO:oejs.ServerConnector:main: Started > ServerConnector@1f021e6c{HTTP/1.1,[http/1.1, h2c, h2c-17, h2c-16, h2c-15, > h2c-14]}{0.0.0.0:9020} > ... > 2016-09-06 13:23:52.721:INFO:oejs.ServerConnector:main: Started > ServerConnector@6fe7aac8{SSL,[ssl, alpn, h2, h2-17, h2-16, h2-15, h2-14, > http/1.1]}{0.0.0.0:9021} > > I used curl to test the server, like the below command, > curl -k --http2 -H "Expect: 100-continue" -d "body" > https://localhost:9021/body > then it just printed the following error: > curl: (92) HTTP/2 stream 1 was not closed cleanly: INTERNAL_ERROR (err 2) > If remove 100-continue header, like, > curl -k --http2 -d "body" https://localhost:9021/body > Or over HTTP, like > curl -k --http2 -H "Expect: 100-continue" -d "body" > http://localhost:9020/body > the results looked fine. > > Is it a Jetty bug on supporting 100-continue over TLS?
It was a bug, tracked here: https://github.com/eclipse/jetty.project/issues/902 -- Simone Bordet ---- http://cometd.org http://webtide.com Developer advice, training, services and support from the Jetty & CometD experts. _______________________________________________ jetty-users mailing list jetty-users@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jetty-users