[
https://issues.apache.org/jira/browse/TS-3960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14975394#comment-14975394
]
ASF GitHub Bot commented on TS-3960:
------------------------------------
Github user jpeach commented on the pull request:
https://github.com/apache/trafficserver/pull/301#issuecomment-151318976
I don't think it is that complex. All the machinery for doing this exists,
it just needs to be tied together in a sightly different way. My view is that
this approach adds complexity in the wrong place (though I definitely agree
that the config file management code can be refactored and simplified). One
approach would be to make an upcall to ```traffic_manager``` that installs a
"temporary watch" (ie. watch the file until the next reconfigure event).
Note that both ```ssl_multicert.config``` and ```remap.config``` have this
issue, so a general mechanism can be used to deal with both cases. Your
proposed solution also fails to update
```proxy.node.config.reconfigure_required``` correctly.
> traffic_line -x doesn't reload SSL certs content
> ------------------------------------------------
>
> Key: TS-3960
> URL: https://issues.apache.org/jira/browse/TS-3960
> Project: Traffic Server
> Issue Type: Bug
> Components: SSL
> Reporter: Zhang Zizhong
> Assignee: Brian Geffon
> Fix For: 6.1.0
>
>
> traffic_line -x doesn't reload when SSL certs change file contents without
> changing the file names.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
