Hey Rawlin-
Remember that the proposed feature does not always bypass the mids- we
already have that with the regional DS types. This is just a failure recovery
behavior.
Conflicts with the DS type is only a small part of the major UX problem we
have today relating to Origin FQDNs. Ways
To me it looks like DS types with go_direct TRUE/False will add more
confusion compared to adding go_direct value as a DS configurable parameter
defaulting it to false except for HTTP_LIVE DNS_LIVE and HTTP_NO_CACHE.
Thanks,
Vijayanand S
On Thu, Jun 21, 2018 at 4:53 AM, Rawlin Peters
wrote:
At this point, I think the Perl tests have rotted so much and I don't want
to put anymore effort into them. I say as long as we have Go coverage
(because the API tests will still go through to Perl if no Go catches the
route), then I'm good.
-Dew
On Tue, Jun 26, 2018 at 8:14 AM Robert Butts
> So, there might be a middle ground. How about this: what if we remove the
> Perl routes from the routes file, and change the functions to immediately
> return an informative error message? That way, if we miss some dynamic
Perl
> still calling the code, we immediately get a useful message, so
The Apache Traffic Control team is pleased to announce the release of
Apache Traffic Control 2.2.0.
Apache Traffic Control allows you to build a large-scale Content Delivery
Network (CDN) using open source. Built around Apache Traffic Server as the
caching software, Traffic Control implements all
I had planned on deleting tests for deleted functions (which have tests in
Go), and starting with functions whose tests aren't depended on by any
other tests, and working our way up. Unless anyone objects.
On Mon, Jun 25, 2018 at 8:17 AM, Rawlin Peters
wrote:
> Alright, so we have a compromise
