[ https://issues.apache.org/jira/browse/TS-4658?focusedWorklogId=28257&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-28257 ]
ASF GitHub Bot logged work on TS-4658: -------------------------------------- Author: ASF GitHub Bot Created on: 07/Sep/16 03:05 Start Date: 07/Sep/16 03:05 Worklog Time Spent: 10m Work Description: GitHub user shinrich opened a pull request: https://github.com/apache/trafficserver/pull/976 TS-4658: Why is TSSslVConnOp API? Pulled TSSslVConnOp from plugin header file and docs. Added it back in internally. You can merge this pull request into a Git repository by running: $ git pull https://github.com/shinrich/trafficserver ts-4658 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/trafficserver/pull/976.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #976 ---- commit f560d00dd207ec50774df7ba5627c3b1e515f59d Author: Susan Hinrichs <shinr...@ieee.org> Date: 2016-09-07T03:03:37Z TS-4658: Why is TSSslVConnOp API? ---- Issue Time Tracking ------------------- Worklog Id: (was: 28257) Time Spent: 10m Remaining Estimate: 0h > Why is TSSslVConnOp API? > ------------------------ > > Key: TS-4658 > URL: https://issues.apache.org/jira/browse/TS-4658 > Project: Traffic Server > Issue Type: Bug > Components: SSL, TS API > Reporter: James Peach > Assignee: Susan Hinrichs > Labels: incompatible > Fix For: 7.0.0 > > Time Spent: 10m > Remaining Estimate: 0h > > {{TSSslVConnOp}} is not used in any APIs; it is basically an internal flag to > determine whether the core should terminate a TLS session or not. Let's > remove it from API and make it internal to {{SSLNetVConnection}}. -- This message was sent by Atlassian JIRA (v6.3.4#6332)