Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-dev] HTTP/2 support in Jetty 9.3.0

Hi Greg,

Thank you for your reply and efforts. Basically, the one thing I want to do is using Curl to send an HTTP/2 GET request, making the server send the required content and, at every time interval, pushing some other pre-defined content. I first changed Jetty's SPDY implementation to make this happen, and using the Chrome browser (SPDY net-internals) everything seems to be working fine.

However, we have a client that heavily relies on the use of Curl, and so we want to use Jetty's HTTP/2 component to achieve the same thing. Unfortunately, as I suggested below, an invalid preface error is returned both from Chrome's browser (39.0), Firefox (34.0) and Curl (7.39.0) when using the compiled, most recent version of the source code from the GitHub project. If you could point me in the right direction, I'd be very grateful.

Kind regards,

Jeroen van der Hooft

On 2014-12-12 09:28, Greg Wilkins 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-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


Back to the top