This Bug Report affects these Traffic Control components:
Traffic Ops
Documentation
Current behavior:
When creating a delivery service, the ordinary regex is of the form .*\.ds-name\..*.
If we need a custom domain, we can create an additional Delivery Service Regex for the exact domain, e.g. my.domain.example.net , of type HOST_REGEXP, without any special regex characters.
But I am able to create same custom domain using HOST_REGEXP option for two or more delivery service.
Which cause duplicate entry in Traffic Server remap.conf file.
there doesn't seem to be any validation in place to prevent that from happening
Expected behavior:
Prevent user to create same custom domain for another delivery service.
Steps to reproduce:
create same custom domain using HOST_REGEXP option for two or more delivery service.
Is there any way to check or validate custom domain regex before creating duplicate?
Because it’s causing t3c script to write duplicate entry in remap.config on edge cache servers.
This Bug Report affects these Traffic Control components:
Current behavior:
When creating a delivery service, the ordinary regex is of the form
.*\.ds-name\..*
. If we need a custom domain, we can create an additional Delivery Service Regex for the exact domain, e.g.my.domain.example.net
, of typeHOST_REGEXP
, without any special regex characters.But I am able to create same custom domain using HOST_REGEXP option for two or more delivery service. Which cause duplicate entry in Traffic Server
remap.conf
file.there doesn't seem to be any validation in place to prevent that from happening
Expected behavior:
Prevent user to create same custom domain for another delivery service.
Steps to reproduce:
create same custom domain using HOST_REGEXP option for two or more delivery service.
Is there any way to check or validate custom domain regex before creating duplicate? Because it’s causing t3c script to write duplicate entry in remap.config on edge cache servers.