[
https://issues.apache.org/jira/browse/TC-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Malenfant updated TC-353:
-------------------------------
Affects Version/s: 2.1.0
2.0.0
1.8.0
Priority: Minor (was: Major)
Description:
If you put a HOST_REGEX of "ccr.example.kabletown.net", it will expand to the
server hostname like "edge01.example.kabletown.net". This makes the
remap.config to have the wrong hostname. This might not affect anything but it
should be changed to something unrelated to a specific prefix.
The code ConfigFile.pm is causing the current behavior :
{code}
my $hname = $ds_type =~ /^DNS/ ? "edge" : "ccr";
my $portstr = "";
...
$map_from =~ s/ccr/$host_name/;
{code}
Component/s: Traffic Ops
Summary: Can't CNAME hostname with "ccr" (was: Can't CNAME
hostname with ccr")
> Can't CNAME hostname with "ccr"
> -------------------------------
>
> Key: TC-353
> URL: https://issues.apache.org/jira/browse/TC-353
> Project: Traffic Control
> Issue Type: Bug
> Components: Traffic Ops
> Affects Versions: 1.8.0, 2.0.0, 2.1.0
> Reporter: Steve Malenfant
> Priority: Minor
>
> If you put a HOST_REGEX of "ccr.example.kabletown.net", it will expand to the
> server hostname like "edge01.example.kabletown.net". This makes the
> remap.config to have the wrong hostname. This might not affect anything but
> it should be changed to something unrelated to a specific prefix.
> The code ConfigFile.pm is causing the current behavior :
> {code}
> my $hname = $ds_type =~ /^DNS/ ? "edge" : "ccr";
> my $portstr = "";
> ...
> $map_from =~ s/ccr/$host_name/;
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
