Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/834
I think I'm ok with this for now, but I really wish we'd done something
similar to TSHttpTxnCacheLookupUrlGet() / TSHttpTxnCacheLookupUrlSet(), but for
the parent selection URL to use. Like
tsapi TSReturnCode TSHttpTxnParentSelectionUrlGet(TSHttpTxn txnp,
TSMBuffer bufp, TSMLoc obj);
tsapi TSReturnCode TSHttpTxnParentSelectionUrlSet(TSHttpTxn txnp,
TSMBuffer bufp, TSMLoc obj);
And then we could either have extended the functionality in the cachekey
plugin (or, make a new plugin). There's generally a problem when a plugin
changes the cache key as well, and the parent selection does not follow the
same lead, the stop-gap solution for that was the ignore query params option.
See
https://issues.apache.org/jira/browse/TS-4025
for some more discussions. My "objection" here is that we're making some
very specific use case changes / features, whereas new APIs, and support for it
in the existing cachekey plugin (which is very feature rich) would solve not
just these two cases, but a lot more.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
