Copilot commented on code in PR #13521: URL: https://github.com/apache/trafficserver/pull/13521#discussion_r3745075458
########## doc/release-notes/whats-new.en.rst: ########## @@ -20,6 +20,242 @@ .. _whats_new: +What's New in ATS v10.2 +======================= + +This version of |ATS| includes 1034 commits from 655 pull requests, with 44 +contributors participating in this development cycle. + +Configuration Reload +-------------------- + +Configuration reload has been rebuilt around a *token* model that makes a +reload an observable, trackable operation rather than a fire-and-forget +signal. Each reload gets a token; handlers report progress and terminal state +against that token, so a reload can be monitored to completion and its +per-handler logs inspected. See :doc:`../developer-guide/config-reload-framework.en`. + +* ``traffic_ctl config reload`` gained ``--monitor``/``-m`` to follow a reload + to completion, ``--show-details``/``-s`` and ``--include-logs``/``-l`` for + per-handler detail, ``--token``/``-t`` to target a specific token, + ``--refresh-int``/``-r`` and ``--timeout``/``-T`` to control polling, and + ``--force``/``-F``. +* ``traffic_ctl config status`` reports reload records for a token, with + ``--count``/``-c`` (numeric or ``all``) and ``--min-level`` to filter log + severity. +* Reload behavior is tunable with :ts:cv:`proxy.config.admin.reload.timeout` + and :ts:cv:`proxy.config.admin.reload.check_interval`. +* Replaced configurations are now destroyed on an ``ET_TASK`` thread rather + than on a network thread, so a large config teardown no longer blocks an + event loop. + +Features +-------- + +* Implement RFC 9213 Targeted HTTP Cache Control. Cache directives can be + targeted at specific caches via headers such as ``CDN-Cache-Control``, + configured through + :ts:cv:`proxy.config.http.cache.targeted_cache_control_headers`, which is + overridable per remap rule. When a targeted header is present it takes + precedence over the standard ``Cache-Control`` header, and the targeted + header is passed downstream so cache hierarchies behave correctly. +* Connect retries to the origin can now back off exponentially, controlled by + :ts:cv:`proxy.config.http.connect_attempts_retry_backoff_base`, instead of + retrying immediately and piling connections onto a struggling origin. +* Origin connect retry limits are now selected by HostDB state: + :ts:cv:`proxy.config.http.connect_attempts_max_retries` for ``UP`` servers, + the new + :ts:cv:`proxy.config.http.connect_attempts_max_retries_suspect_server` for + ``SUSPECT``, and no retries for ``DOWN``. The retry limits were not + previously applied according to origin state, so this is a necessary + incompatible change. See :ref:`upgrading` before deploying. +* :ts:cv:`proxy.config.http.connect.down.policy` gained option ``3``, which + counts inactive connections as failures. +* Snowflake IDs, 64-bit organizationally unique identifiers, are now used for + connection IDs so they are unique across restarts and typically across + instances in a CDN. +* TLS certificate compression is supported in both directions, configured with + :ts:cv:`proxy.config.ssl.server.cert_compression.algorithms` and + :ts:cv:`proxy.config.ssl.client.cert_compression.algorithms`. +* Certificate loading can now be parallelized with + :ts:cv:`proxy.config.ssl.server.multicert.concurrency`. +* :file:`sni.yaml` supports session ticket overrides. +* QUIC token secrets are configurable via + ``proxy.config.quic.server.token_key.filename``. Review Comment: This references a records.yaml setting as a literal code span. Since this is a real configuration record (it is documented as a ts:cv entry), using :ts:cv: here would provide a consistent cross-reference and ensure it’s searchable/linkable like the other records in this list. This issue also appears on line 116 of the same file. ########## doc/release-notes/whats-new.en.rst: ########## @@ -20,6 +20,242 @@ .. _whats_new: +What's New in ATS v10.2 +======================= + +This version of |ATS| includes 1034 commits from 655 pull requests, with 44 +contributors participating in this development cycle. Review Comment: The PR description says the changelog was generated from a 10.2.0 milestone with 650 PRs, but this sentence states 655 pull requests. This should be reconciled so release metadata is consistent (either update this count or adjust the PR description to match the milestone totals actually used). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
