[jira] [Reopened] (TS-841) support TLS NextProtocol negotiation

["Leif Hedstrom (Reopened) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TS-841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leif Hedstrom reopened TS-841:
------------------------------


It seems when accept threads are disabled, the VC is not properly reset? It used to be, I'm pretty sure, that when we accept on the net thread, we use a proxy allocator for allocating the VC. I remember adding some code around that case, to assure we release the VC on the correct freelist (proy allocator without accept thread, global freelist when accept threads are enabled).

Perhaps this somehow got reverted ? I can definitely trigger the assert after a few requests with accept threads disabled.
                
> support TLS NextProtocol negotiation
> ------------------------------------
>
>                 Key: TS-841
>                 URL: https://issues.apache.org/jira/browse/TS-841
>             Project: Traffic Server
>          Issue Type: New Feature
>          Components: HTTP, SSL
>            Reporter: Leif Hedstrom
>            Assignee: James Peach
>             Fix For: 3.1.3
>
>         Attachments: 0001-TS-841-Move-SSLNetAccept-and-SSLNetProcessor-into-ep.patch, 0002-TS-841-Sprinkle-some-const-pixie-dust-on-the-SSL-cla.patch, 0003-TS-841-Propagate-zero-length-read-events-through-SSL.patch, 0004-TS-841-Load-plugins-after-opening-sockets.patch, 0005-TS-841-support-TLS-NextProtocol-negotiation.patch
>
>
> In order to make it possible to write protocol handlers like SPDY, we need to negotiate NPN protocol before entering the HTTP SM. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira