Re: [jetty-users] How not to support drafts of H2 (if not doing so is re

[Greg Wilkins <gregw@xxxxxxxxxxx>]

Travis,

Dropping the drafts from ALPN should be sufficient for h2, but will not work if you use h2c.

I've created https://github.com/eclipse/jetty.project/issues/689 and hope to have something in 9.3.11

cheers

On 5 July 2016 at 16:40, Travis Spencer <travislspencer@xxxxxxxxx> wrote:

Hi There,

When embedding Jetty 9.3.10.v20160621, should we drop support for the
drafts of HTTP/2? Is this a recommended best practice or is supporting
the drafts best for now? Most browsers seem to have dropped support
for the drafts already, so we're thinking it's best not to support
them either. Is that right? If so, how can support for the drafts be
removed from a Jetty instance?

It seems that HTTP2ServerConnectionFactory does not accept a list of
protocols whereas ALPNServerConnectionFactory does. Is it that one
should specify the protocols in the ALPN factory, causing clients to
only be able to negotiate the protocols given to
ALPNServerConnectionFactory. Consequently, the fact that
HTTP2ServerConnectionFactory always supports the drafts is
inconsequential because no client will ever be able to negotiate those
pre-release versions of the spec?

TIA!

--

Regards,

Travis Spencer

_______________________________________________
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

--

Greg Wilkins <gregw@xxxxxxxxxxx> CTO http://webtide.com