[
https://issues.apache.org/jira/browse/TS-2805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13997001#comment-13997001
]
Bryan Call commented on TS-2805:
--------------------------------
The order looks like it needs to be changed:
Protocol selection
It's expected that a client will have a list of protocols that it supports, in
preference order, and will only select a protocol if the server supports it. In
that case, the client SHOULD select the first protocol advertised by the server
that it also supports. In the event that the client doesn't support any of
server's protocols, or the server doesn't advertise any, it SHOULD select the
first protocol that it supports.
There may be cases where the client knows, via other means, that a server
supports an unadvertised protocol. In these cases the client can simply select
that protocol.
https://tools.ietf.org/id/draft-agl-tls-nextprotoneg-03.html#rfc.section.4
> Client connections are connecting with SPDY 3 instead of 3.1
> ------------------------------------------------------------
>
> Key: TS-2805
> URL: https://issues.apache.org/jira/browse/TS-2805
> Project: Traffic Server
> Issue Type: Bug
> Components: SPDY
> Reporter: Bryan Call
> Assignee: Brian Geffon
> Labels: spdy, yahoo
> Fix For: 5.0.0
>
>
> When testing with Chrome spdycat it is preferring to connect with SPDY 3:
> [bcall@cat ~]$ spdycat -v https://l10.ycs.sjb.yahoo.com
> [ 0.025] NPN select next protocol: the remote server offers:
> * spdy/3
> * spdy/3.1
> * http/1.0
> * http/1.1
> NPN selected the protocol: spdy/3
--
This message was sent by Atlassian JIRA
(v6.2#6252)
