The modules also control proper order of execution for the various components needed by that module and its dependent modules. It would be entirely too messy (and not forward compatible) to run without the module system. Also, when you upgrade your Java version, you will get mysterious failures as the alpn-boot version is Java version specific. (we have a new one for Java 8u51 for example) Using your technique, you'll wind up with no warning about an incompatible alpn-boot jar.
Since you are using SSL, you'll want to keep your Java version up to date. Which means you'll be upgrading your Java version about 6 times a year. Joakim Erdfelt / [email protected] On Wed, Jul 29, 2015 at 9:07 AM, Michele Rossi <[email protected]> wrote: > hi, > > the problem with just using --module=http2 is that you end up including a > sub-module such as alpn-impl/alpn-1.8.0_45.mod which contains this: > > [exec] > -Xbootclasspath/p:lib/alpn/alpn-boot-8.1.3.v20150130.jar > > This means that a new VM is spawned from the original one which I really > don't like. > > I prefer to pass the correct boot classpath to jetty by using the > JAVA_OPTIONS environment variable which is used by the init.d script to > launch jetty. > > I don't think this has anything to do with the problem though. > > As I said HTTP2 works correctly in Chrome which wouldn't be possible if I > had messed the config so bad. > > I am sure I have done something wrong somewhere though, for example is > this line correct? > > jetty.alpn.protocols=h2,h2-17,h2-16,h2-15,h2-14,http/1.1 > > If I put http/1.1 first then Chrome does not seem to negotiate h2. > > I am wondering whether that would fix IE11 though, will try and let the > group know. > > > thanks, > Michele > > > > On 29 July 2015 at 18:00, <[email protected]> wrote: > >> Send jetty-users mailing list submissions to >> [email protected] >> >> To subscribe or unsubscribe via the World Wide Web, visit >> https://dev.eclipse.org/mailman/listinfo/jetty-users >> or, via email, send a message with subject or body 'help' to >> [email protected] >> >> You can reach the person managing the list at >> [email protected] >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of jetty-users digest..." >> >> Today's Topics: >> >> 1. IE11 shows only "invalid_preface" when HTTP2 is enabled >> (Michele Rossi) >> 2. Re: IE11 shows only "invalid_preface" when HTTP2 is enabled >> (Joakim Erdfelt) >> >> >> ---------- Forwarded message ---------- >> From: Michele Rossi <[email protected]> >> To: [email protected] >> Cc: >> Date: Wed, 29 Jul 2015 16:47:27 +0200 >> Subject: [jetty-users] IE11 shows only "invalid_preface" when HTTP2 is >> enabled >> 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. >> >> thanks, >> Michele >> >> >> >> >> ---------- Forwarded message ---------- >> From: Joakim Erdfelt <[email protected]> >> To: JETTY user mailing list <[email protected]> >> Cc: >> Date: Wed, 29 Jul 2015 08:26:56 -0700 >> Subject: Re: [jetty-users] IE11 shows only "invalid_preface" when HTTP2 >> is enabled >> Do not enable http2 that way >> If you are using --lib= you are not enabling it properly. >> >> Use --module=http2 instead of those 3 --lib lines. >> >> >> Joakim Erdfelt / [email protected] >> >> On Wed, Jul 29, 2015 at 7:47 AM, 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. >>> >>> thanks, >>> Michele >>> >>> >>> >>> _______________________________________________ >>> 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 >>> >> >> >> _______________________________________________ >> 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 >> > > > _______________________________________________ > 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 >
_______________________________________________ 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
