Hmm, this was the kind of behaviour of NPN, maybe that influenced the API of that toolkit?
I imagine that the toolkit will decide itself then what protocol is negotiated. That would mean that the directive ProtocolsHonorOrder has no longer an effect. Am I right? I do not think that is what we want. //Stefan > Am 26.08.2015 um 17:02 schrieb Edward Lu <[email protected]>: > > I was experimenting with the new support for declaring protocols for e.g. > ALPN, but with an SSL toolkit other than openssl. This one wants us to pass > the entire list of all the protocols the server supports in advance; later, > we can request the one protocol that the toolkit negotiated. > > It looks like the protocol_propose hook allows us to only grab a subset of > the protocols - i.e. it expects us to have the protocol list that the client > sends us. I've attached a patch which modifies the protocol_propose hook's > interface (documentation), allowing us to get all of the protocols supported > by the server. I also modified h2's implementation of the hook to reflect the > interface change. > > Let me know if anyone sees a problem. > > <all_protos.diff> <green/>bytes GmbH Hafenweg 16, 48155 Münster, Germany Phone: +49 251 2807760. Amtsgericht Münster: HRB5782
