Hi, On Wed, Jul 29, 2015 at 4:47 PM, Michele Rossi <[email protected]> wrote: > hi, > I am experimenting with Jetty 9.3.0 and HTTP2 which I have enabled as > follows: > > --lib=lib/http2/*.jar > --lib=lib/jetty-alpn-client-${jetty.version}.jar > --lib=lib/jetty-alpn-server-${jetty.version}.jar > > etc/jetty-http2.xml > etc/jetty-alpn.xml > > > It all works fine on Chrome (and thanks to a handy plugin I can see that > Chrome is actually using HTTP2) but on IE11 the page doesn't render at all > and all I get is "invalid_preface" on a white page. > > I am probably doing something glamorously wrong - any tips much appreciated.
If it works in Chrome but not IE, perhaps it's IE doing something wrong. The only way to know is to compare the TCP dumps for both cases. The string "invalid_preface" is something we send from the server if the preface bytes do not match what mandated by the spec. But it could also be something IE does. Again, TCP dumps to figure out. Having said that, follow what Joakim says about the modules: it's much easier and removes one variable to this issue. -- Simone Bordet ---- http://cometd.org http://webtide.com Developer advice, training, services and support from the Jetty & CometD experts. _______________________________________________ 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
