Apache Traffic Control 5.1.1 is available here:
maxRequestHeaderBytes on a per delivery service basisweight parameter of parent.config is a floattraffic_ops/v3-client documentation for details.ip_allow.config such that PURGE requests are allowed over localhost
2020082700000000_server_id_primary_key.sql trying to create multiple primary keys when there are multiple schemas.2020062923101648_add_deleted_tables.sqlmove_lets_encrypt_to_acme.sql, add_max_request_header_size_delivery_service.sql, and server_interface_ip_address_cascade.sql past last migration in 5.0.0parent_reval_pending for servers in a Flexible Topology CDN-specific on GET /servers/{{name}}/update_status
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 5.0.0 is available here:
traffic_ops_ort.pl Perl script to the Go language. See traffic_ops_ort/t3c/README.md./topologies, to create, read, update and delete flexible topologies.astats_over_http plugin CSV supportastats_over_http plugin for ATS now supports outputting data in CSV format when
given the text/csv MIME-Type in the Accept header. Traffic Monitor is capable of requesting this new format (which
is faster to parse than the JSON format) in its Profile's http_polling_format Parameter.stats_over_http plugin, CSV format using that
health.polling.format value is also supported - but note that one must also install the system_stats plugin to
provide all of the data necessary for Traffic Monitor's evaluations. Note also that this usage requires
ATS version 9 or higher.
xmppId) on Traffic Portals' server summary pageIf-Match and If-Unmodified-Since HTTP headers to Traffic Ops and its native Go clientUser-Agent string to Traffic Router log outputlocationByDeepCoverageZone to the crs/stats/ip/{ip} endpoint in the Traffic Router APItraffic_portal_properties.json (default is 7 days) and can be overridden by the user in Traffic Portal
GET /api/x/cdns/capacity gives back 500, with the message capacity was zero/jobs and /jobs/:id Traffic Ops API routes to allow falling back to Perl via the routing blacklistcoalesce_number_v6 Parameter.POST deliveryservices/request (designed to simple send an email) regression which erroneously required deep caching type and routing name/deliveryservice_stats regression restricting metric type to a predefined set of values__RANGE_DIRECTIVE__ directive to allow inserting the Range Directive after the Raw Remap text. This allows Raw Remaps which manipulate the Rangecreate_tables.sql be run concurrently without issue
tmconfig.backup to that of a GET request to /cdns/{{name}}/configs/monitoring instead of a transformed map
github.com/apache/trafficcontrol/traffic_ops/client is now deprecated in favor of versioned import paths e.g. github.com/apache/trafficcontrol/traffic_ops/v3-client.
atstccfg.Apache Traffic Control 4.1.1 is available here:
--traffic_ops_insecure=<0|1> optional option to traffic_ops_ort.pl__RANGE_DIRECTIVE__ override
SYNCDS runs by default
insecure option in traffic_ops_golang in favor of "tls_config": { "InsecureSkipVerify": <bool> }