Apache Traffic Control 4.1.0 is available here:
__RANGE_DIRECTIVE__ directive
allow_ip6
profile parameter to include the IPv6 addresses of your Traffic Monitors,
otherwise they will fail to poll over IPv6 and consider those caches to be
unavailable over IPv6)
db/admin.pl script has now been removed. Please use the
db/admin binary instead.
atstccfg.
It is essential that you verify the integrity of the downloaded files using the PGP or MD5 signatures.
The PGP signatures can be verified using PGP or GPG. First download the KEYS as well as the `ASC` signature file for the relevant distribution. Make sure you get these files from the main distribution directory, rather than from a mirror. Then verify the signatures using:
% pgpk -a KEYS % pgpv apache-trafficcontrol-4.1.0.tar.gz.ascor% pgp -ka KEYS % pgp apache-trafficcontrol-4.1.0.tar.gz.ascor% gpg --import KEYS % gpg --verify apache-trafficcontrol-4.1.0.tar.gz.asc apache-trafficcontrol-4.1.0.tar.gz
$ gpg --verify apache-trafficcontrol-4.1.0.tar.gz.asc apache-trafficcontrol-4.1.0.tar.gz
gpg: Signature made Tue Feb 11 09:38:30 2020 MST
gpg: using RSA key BF4A8D7307B8EEC7BFB4D8CB8A0712500C70C06E
gpg: Good signature from "Rawlin Peters (apache signing key) " [ultimate]
Additionally, you should verify the SHA signature on the files. A unix program called `sha` or `shasum` is included in many unix distributions. It is also available as part of GNU Textutils. An MD5 signature (deprecated) consists of 32 hex characters, and a SHA512 signature consists of 128 hex characters. Ensure your generated signature string matches the signature string published in the files above.
Apache Traffic Control 4.0.0 is available here:
MID caches will serve all
delivery services in a given CDN, but this feature can be used to allow a only a subset
of MID caches to serve certain delivery services (based on the server
capabilities assigned to the MID caches and required by the delivery
services). See the blueprint
routing_blacklist field in
cdn.conf, enable certain whitelisted Go routes to be handled by Perl
instead (via the perl_routes list) in case a regression is found in the Go
handler, and explicitly disable any routes via the disabled_routes list.
Requests to disabled routes are immediately given a 503 response. Both fields are lists
of Route IDs, and route information (ID, version, method, path, and whether or not it
can bypass to Perl) can be found by running ./traffic_ops_golang
--api-routes. To disable a route or have it bypassed to Perl, find its Route
ID using the previous command and put it in the disabled_routes or perl_routes
list, respectively.
Expires cookie header was not being set
properly in responses. Also, added the Max-Age cookie header in responses.
/cachegroup_fallbacks endpoint is now deprecated. That
functionality was added to the /cachegroups API.
db/admin.pl script is now deprecated. There is a new Go
db/admin binary to replace the Perl db/admin.pl script, which will be
removed in a future release. The new db/admin binary is essentially a drop-in
replacement for db/admin.pl since it supports all of the same commands and options;
therefore, it should be used in place of db/admin.pl for all the same tasks.
influxdb.conf config file has changed from
traffic_ops/app/conf/production/influxdb.conf to traffic_ops/app/conf/influxdb.conf.
Please move any existing influxdb.conf to the new location.
/api/1.1/osversions endpoint (used for ISO generation) now expects the
Perl osversions.cfg configuration file to be JSON. Added a traffic_ops/app/bin/osversions-convert.pl
script to convert the osversions.cfg file from Perl to JSON as part of the
/osversions endpoint rewrite.
/foo?a=1 and
/foo?a=2 each return unique content, you should add a to the
list of consistent hash query parameters for that delivery service. This allows clients
to be routed to edges for that content more efficiently.
client.steering.forced.diversity
Traffic Router profile parameter.
REFUSED DNS answers if the zone priming
execution did not complete within the configured zonemanager.init.timeout
period.
rhi. This defaults to '-' and is only used when EDNS0
client subnet extensions are enabled and a client subnet is present in the request. When
enabled and a subnet is present, the subnet appears in the chi field and
the resolver address is in the rhi field.
__RETURN__ in delivery
service edge/mid header rewrite rules, regex remap expressions, raw remap text and
traffic router additional request/response headers.
atstccfg, installed with ORT. Includes all configs. Includes a plugin
system.