[
https://issues.apache.org/jira/browse/TS-3438?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sudheer Vinukonda reopened TS-3438:
-----------------------------------
This issue seems to still exist despite the assert. In fact, the corruption
seems so bad that, the npn list has garbage data including the entire server
cert!
So, it seems that the problem is not during the creation of the list, but,
something else when using it. Reopening for further investigation.
> npn list being created with garbage data
> ----------------------------------------
>
> Key: TS-3438
> URL: https://issues.apache.org/jira/browse/TS-3438
> Project: Traffic Server
> Issue Type: Bug
> Components: SSL
> Affects Versions: 5.3.0
> Reporter: Sudheer Vinukonda
> Assignee: Sudheer Vinukonda
> Fix For: 6.0.0
>
>
> We noticed that occasionally upon a restart, the npn list built by ATS has
> garbage data (additional null bytes), resulting in the client failing to
> decode the ServerHello correctly. The problem would always go away with a
> restart and is hard to reproduce.
> Here's a trace that shows the good vs bad npn lists in the ServerHello:
> bad npn list (with spdy and http enabled):
> {code}
> Extension: next_protocol_negotiation
> Type: next_protocol_negotiation (0x3374)
> Length: 36
> Next Protocol Negotiation
> Protocol string length: 8
> Next Protocol: spdy/3.1
> Protocol string length: 6
> Next Protocol: spdy/3
> Protocol string length: 8
> Next Protocol: http/1.1
> Protocol string length: 8
> Next Protocol: http/1.0
> Protocol string length: 0
> Protocol string length: 0
> {code}
> good npn list:
> {code}
> Extension: next_protocol_negotiation
> Type: next_protocol_negotiation (0x3374)
> Length: 34
> Next Protocol Negotiation
> Protocol string length: 8
> Next Protocol: spdy/3.1
> Protocol string length: 6
> Next Protocol: spdy/3
> Protocol string length: 8
> Next Protocol: http/1.1
> Protocol string length: 8
> Next Protocol: http/1.0
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
