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