[
https://issues.apache.org/jira/browse/TS-4703?focusedWorklogId=28859&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-28859
]
ASF GitHub Bot logged work on TS-4703:
--------------------------------------
Author: ASF GitHub Bot
Created on: 12/Sep/16 19:07
Start Date: 12/Sep/16 19:07
Worklog Time Spent: 10m
Work Description: Github user shinrich commented on a diff in the pull
request:
https://github.com/apache/trafficserver/pull/1007#discussion_r78434727
--- Diff: iocore/net/SSLUtils.cc ---
@@ -2055,8 +2055,12 @@ SSLParseCertificateConfiguration(const
SSLConfigParams *params, SSLCertLookup *l
// load the global ticket key for later use
REC_ReadConfigStringAlloc(ticket_key_filename,
"proxy.config.ssl.server.ticket_key.filename");
- ats_scoped_str
ticket_key_path(Layout::relative_to(params->serverCertPathOnly,
ticket_key_filename));
- global_default_keyblock = ssl_create_ticket_keyblock(ticket_key_path);
// this function just returns a keyblock
+ if (ticket_key_filename && strcmp(ticket_key_filename, "\"\"") != 0) {
--- End diff --
Nope as noted with James' comment. Was a workaround for the keyblock
problem. Gone with the rebase.
Issue Time Tracking
-------------------
Worklog Id: (was: 28859)
Time Spent: 8h 10m (was: 8h)
> Adds an API call to retrieve transaction protocol
> -------------------------------------------------
>
> Key: TS-4703
> URL: https://issues.apache.org/jira/browse/TS-4703
> Project: Traffic Server
> Issue Type: Improvement
> Components: TS API
> Reporter: Petar Penkov
> Assignee: Susan Hinrichs
> Fix For: 7.0.0
>
> Time Spent: 8h 10m
> Remaining Estimate: 0h
>
> It would be useful if there was a way to retrieve the underlying protocol for
> a given transaction through the tsapi at the very least for plugin logging
> purposes. This can be achieved with a very simple method since this
> information is already available internally.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
