If all it meant was that currently cached content would effectively be
expired, I wouldn't see this as being anything more than an strong note.
But as I'm sure people have created their own tools for building the page
cache keys to forcibly expire them [and not yet taken advantage of that
function
Ticket #20346 is the request that cache keys should be generated from a
request's full URL rather than path, and the proposed implementation of
this is backwards-incompatible.
Because the existing keys are a hash of the path, and so, so far as I know,
we do not have the original path needed to mig
