You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "James Peach (JIRA)" <ji...@apache.org> on 2014/04/24 01:46:16 UTC

[jira] [Commented] (TS-2744) TSNetAcceptNamedProtocol asserts for unknown protocols

    [ https://issues.apache.org/jira/browse/TS-2744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13979102#comment-13979102 ] 

James Peach commented on TS-2744:
---------------------------------

There's no "unknown" value in {{TSProtoType}}, but I think it should be safe to mark unrecognized protocols as {{TS_PROTO_TLS}}.

> TSNetAcceptNamedProtocol asserts for unknown protocols
> ------------------------------------------------------
>
>                 Key: TS-2744
>                 URL: https://issues.apache.org/jira/browse/TS-2744
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: TS API
>            Reporter: James Peach
>
> {{TSNetAcceptNamedProtocol}} is supposed to accept arbitrary strings because it lets you implement your own protocol plugin over TLS, using NPN or ALPN to demux the session. TS-2431 broke this by adding an assertion to {{SSLNextProtocolSet::NextProtocolEndpoint::NextProtocolEndpoint}} when an unknown protocol is registered. A large part of the point of this API is to allow you to register your own protocol.



--
This message was sent by Atlassian JIRA
(v6.2#6252)