[trafficserver] branch 9.0.x updated: Upgrade warning about cachekey behavior

[zw...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

zwoop pushed a commit to branch 9.0.x
in repository https://gitbox.apache.org/repos/asf/trafficserver.git


The following commit(s) were added to refs/heads/9.0.x by this push:
     new 5cb5590  Upgrade warning about cachekey behavior
5cb5590 is described below

commit 5cb5590efb4c96f91d064358eeb06c031c9a1822
Author: Leif Hedstrom <zw...@apache.org>
AuthorDate: Thu Oct 24 20:48:10 2019 -0600

    Upgrade warning about cachekey behavior
---
 doc/release-notes/upgrading.en.rst | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/doc/release-notes/upgrading.en.rst b/doc/release-notes/upgrading.en.rst
index 9f9204f..b70c93c 100644
--- a/doc/release-notes/upgrading.en.rst
+++ b/doc/release-notes/upgrading.en.rst
@@ -42,6 +42,12 @@ Cache
 The cache in this releases of ATS is compatible with previous versions of ATS. You would not expect
 to lose your cache, or have to reinitialize the cache when upgrading.
 
+However, due to changes in how remap plugins are processed, your cache key *might* change. In versions
+to v9.0.0, the first plugin in a remap rule would get the pristine URL, and subsequent plugins would
+get the remapped URL. As of v9.0.0, **all** plugins now receive the remapped URL. If you are using
+a plugin that modifies the cache key, e.g. :ref:`admin-plugins-cachekey`, if it was evaluated first
+in a remap rule, the behavior (input) changes, and therefore, cache keys can change!
+
 Configuration changes
 ---------------------
 The following incompatible changes to the configurations have been made in this version of ATS.