Re: [jetty-dev] [jetty-users] HTTP/2 support in Jetty 9.3.0

[Jeroen van der Hooft <jeroen.vanderhooft@xxxxxxxxxxxxxx>]

As a reference, using nghttp2-0.6.7  (which curl depends upon to support HTTP/2) results in the following:

nghttp https://localhost:8443 -v
[ERROR] HTTP/2 protocol was not selected. (nghttp2 expects h2-14)
Some requests were not processed. total=1, processed=0

nghttp https://webtide.com -v
[ERROR] HTTP/2 protocol was not selected. (nghttp2 expects h2-14)
Some requests were not processed. total=1, processed=0

whereas this does work for nghttp2.org or a local nghttp2 server:

nghttp https://localhost:3000 -v
[  0.003][NPN] server offers:
          * h2-14
The negotiated protocol: h2-14
[  0.004] send SETTINGS frame <length=12, flags=0x00, stream_id=0>
          (niv=2)
          [SETTINGS_MAX_CONCURRENT_STREAMS(0x03):100]
          [SETTINGS_INITIAL_WINDOW_SIZE(0x04):65535]
[  0.004] send HEADERS frame <length=33, flags=0x05, stream_id=1>
          ; END_STREAM | END_HEADERS
          (padlen=0)
          ; Open new stream
          :authority: localhost:3000
          :method: GET
          :path: /
          :scheme: https
          accept: */*
          accept-encoding: gzip, deflate
          user-agent: nghttp2/0.6.7

On 2014-12-12 12:28, Jeroen van der Hooft wrote:

Dear Greg,

http://curl.haxx.se/download.html provides the latest released curl version, 7.39.0

I am using yesterday's version at https://github.com/eclipse/jetty.project, repo commit 2b196a9ae194d61fefbec0938b328ad474fd2b6b

I can use curl with HTTP/2 to hit e.g. nghttp2.org:

< HTTP/2.0 200
< accept-ranges:bytes
< content-length:28617
< content-type:text/html
< date:Fri, 12 Dec 2014 11:22:01 GMT
< etag:"547b2e3d-6fc9"
< last-modified:Sun, 30 Nov 2014 14:48:29 GMT
< server:nghttpx nghttp2/0.6.8-DEV
< via:1.1 nghttpx
< strict-transport-security:max-age=3153600

Using the same approach, an invalid preface error is thrown. Both from curl as from the browser.

Kind regards,

Jeroen van der Hooft

On 2014-12-12 12:06, Greg Wilkins wrote:

hmmm I can't find curl 7.39.0 for ubuntu...

On 12 December 2014 at 12:02, Greg Wilkins <gregw@xxxxxxxxxxx> wrote:

What is the last commit in your repo you are using?   Mine is a71cc6978ae9f25fb378813044c9415944eb3b74

what github URL?

Can curl get anything from webtide.com with http2 for you?

On 12 December 2014 at 11:59, Greg Wilkins <gregw@xxxxxxxxxxx> wrote:

I just tried Chromium 39.0.2171.65 Ubuntu 14.04 (64-bit) and it connects fine with HTTP2

I ran the Http2Server tets harness locally and hit it with https://localhost:8443/test and got:

Hello from Jetty using HTTP/2
uri=/test
session=5cpb54kwpmtz2d0vgp99mr5z
date=Fri Dec 12 11:49:56 CET 2014

So looks OK. 

I pointed it at webtide.com and I think it is http/2 - no easy way to tell, but it is using http/2 header formats :scheme: :path: etc.

On 12 December 2014 at 09:28, Greg Wilkins <gregw@xxxxxxxxxxx> wrote:

Jeroen,

We've been mostly testing with FF nightly, although I have also had positive reports of curl working fine.

Note that www.webtide.com is running HTTP/2 so you should be able to test there as well.

I'll give chrome a go today and report back.

cheers

On 11 December 2014 at 11:15, Jeroen van der Hooft <jeroen.vanderhooft@xxxxxxxxxxxxxx> wrote:

Dear all,

Last August, developers announced that draft 14 of HTTP/2 is now live. I am currently using the provided source code of Jetty 9.3.0 of the GitHub project, which comes with an HTTP/2 component and associated HTTP/2 module. Using the default configurations, the server is started with HTTP/2 enabled:

INFO:oejs.ServerConnector:main: Started ServerConnector@3796751b{HTTP/1.1,[http/1.1]}{0.0.0.0:8080}
INFO:oejs.ServerConnector:main: Started ServerConnector@12f41634{SSL,[ssl, alpn, h2-15, h2-14]}{0.0.0.0:8443}
INFO:oejs.Server:main: Started @887ms

However, from the Google Chrome browser (using --enable-spdy4) or using curl 7.39.0 (which comes with support for HTTP/2), an invalid preface error is returned. According to the latest draft, this means that the peer does not support HTTP/2. Any idea what may cause this problem to arise?

Kind regards,

Jeroen van der Hooft
_______________________________________________
jetty-dev mailing list
jetty-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-dev

_______________________________________________
jetty-users mailing list
jetty-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jetty-users