Github user pbchou commented on the issue:
https://github.com/apache/trafficserver/pull/834
@zwoop I implemented the two API calls that you recommended above (along
with the two corresponding ts_lua API calls). However, I did not see a graceful
way to get the URL set via the API calls to the ParentConsistentHash.cc hash
generation function since it is only passing the request_data and not the
entire HTTP transaction. As a work-around, I wrote the URL into an "@ATS..."
MIME field to accomplish the data exchange. The plus to this is that you can
set the MIME field without using the API (and it does not need to be a valid
URL if set with this method). The hash generation will just hash the contents
of this MIME field if it is defined (and ignore the other options maxdirs,
fname, and qstring). I retained the maxdirs and fname enhancements in the
earlier commit as I have not yet sold my users on this new approach.
---
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.
---
