from wherever you decide)
and
> > use that value to update the db.
> >
> > jeremy
> >
> >
> >
> > On Tue, Aug 15, 2017 at 9:14 AM, Peters, Rawlin <
> rawlin_pet...@comcast.com
> > > wrote:
> >
> > that would require a new version of the API, no?
> >
> > Hence my suggestion for a default. But, yes, i forgot about the per CDN
> > thing.
> >
> > Jeremy
> >
> > On Mon, Aug 14, 2017 at 5:25 PM, Peters, Rawlin <
s to be set before upgrade and B) TR will now
> ignore
> > the setting in the config file. Ideally we would remove the param from
> the
> > default config and the need for the param in the code.
> >
> > On Wed, Aug 9, 2017 at 4:28 PM, Peter
“http.routing.name” parameter in the
Traffic Router’s “http.properties” file will be ignored (same with the
“dns.routing.name”
parameter in “dns.properties” which I’m not sure can even be changed safely
today).
Thoughts?
--Rawlin
On 8/4/17, 10:19 AM, "Peters, Rawlin" wrote:
> Thanks,
> Zhilin
>
>
> On 8/5/17, 3:51 AM, "Eric Friedrich (efriedri)"
wrote:
>
>
>> On Aug 4, 2017, at 3:09 PM, Peters, Rawlin
wrote:
>>
>> Ok, it makes sense that if it can support fully customized DS domain
names
Zhilin
On 8/5/17, 3:51 AM, "Eric Friedrich (efriedri)" wrote:
> On Aug 4, 2017, at 3:09 PM, Peters, Rawlin
wrote:
>
> Ok, it makes sense that if it can support fully customized DS domain
names, there would be
>
heir own domain without needing to CNAME over to the CDN
(and play the corresponding games with HTTPS certs)
—Eric
On Aug 4, 2017, at 12:37 PM, Peters, Rawlin
mailto:rawlin_pet...@comcast.com>> wrote:
@Dave @Eric
I have my current code pushed to my fork, an
rie...@cisco.com><mailto:efrie...@cisco.com
> ><mailto:efrie...@cisco.com%3e>>
> wrote:
>
> Hey Rawlin-
> Zhilin has also been working on a very similar feature which was
> proposed on this mailer last month:
> https://lists.apach
v.trafficcontrol.apache.org%3E
> <
>
https://lists.apache.org/thread.html/51d7ed1ae65a3697c39edd00236e6f3897da37ef5b24ac452a17cabb@
> >
>
> Can you please work him to ensure we don’t duplicate work and that if both
> solutions are needed they will work t
Sorry, Outlook converted my numbered list poorly. I’ve corrected the numbering
(items 1-3) below.
On 8/3/17, 1:52 PM, "Peters, Rawlin" wrote:
Hello All,
I’ve been working on adding support for configurable per-CDN and
per-DeliveryService routing names [1] (what are
Hello All,
I’ve been working on adding support for configurable per-CDN and
per-DeliveryService routing names [1] (what are currently hardcoded/defaulted
to ‘edge’ and ‘tr’ for DNS and HTTP Delivery Services, respectively), and I
have a few things to propose.
1. Add a column to the CDN tab
Hey all,
I believe I’ve found an obsolete/broken API endpoint [1] that might be a good
candidate for removal. Here is an example request:
GET /api/1.2/cdns/mycdn/configs/routing
This will return a json object that looks like the following:
{
“response”: {
“trafficServers”: […],
12 matches
Mail list logo
