[
https://issues.apache.org/jira/browse/TC-187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16114618#comment-16114618
]
ASF GitHub Bot commented on TC-187:
-----------------------------------
Github user rawlinp commented on the issue:
https://github.com/apache/incubator-trafficcontrol/pull/360
@zhilhuan can you please rebase this PR?
This PR also seems to fix an issue we'll have once per-DeliveryService
routing names are implemented soon. Basically, if a DNS DS starts using the DNS
routing name "my-edge" rather than the default "edge", the new hostname will
mismatch the hostname used in the SSL cert. Your PR seems to address that
issue, which is helpful in addition to the issue of changing the xml_id.
> Update delivery service makes SSL keys invalid
> ----------------------------------------------
>
> Key: TC-187
> URL: https://issues.apache.org/jira/browse/TC-187
> Project: Traffic Control
> Issue Type: Bug
> Components: Traffic Ops
> Reporter: Zhilin Huang
> Assignee: Zhilin Huang
> Labels: ssl, xml-id
>
> Modify xml-id or subdomain in a https delivery service will make existing SSL
> keys invalid.
> And there is problem to generate keys if using "http and https" together with
> 1 host_regex, and 1 path_regex.
> BTW, the certificate returned by RESTful API is not consistent with that GUI.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
