If the peer who selects the application protocol doesn't find a match it will just select the last protocol it advertised support for. This is used in cases where a "best effort" is desired to talk even if there is no matching protocol, and the assumption is the "most general" fallback protocol is typically listed last.
If the peer who selects the application protocol doesn't find a match it will just select the last protocol it advertised support for. This is used in cases where a "best effort" is desired to talk even if there is no matching protocol, and the assumption is the "most general" fallback protocol is typically listed last.
This may be illegal for some RFCs but was observed behavior by some SSL implementations, and is supported for flexibility/compatibility.
If the peer who selects the application protocol doesn't find a match it will pretend no to support the TLS extension by not advertising support for the TLS extension in the handshake. This is used in cases where a "best effort" is desired to talk even if there is no matching protocol.
If the peer who selects the application protocol doesn't find a match it will pretend no to support the TLS extension by not advertising support for the TLS extension in the handshake. This is used in cases where a "best effort" is desired to talk even if there is no matching protocol.