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 < [email protected]> 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 > [email protected] > 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 [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jetty-users
