Github user gtenev commented on the issue:
https://github.com/apache/trafficserver/pull/837
@zwoop thanks for reviewing!
As far as can tell the escalate plugin was implemented later then the
HttpHdr caching and the caching implementation does not support its use-case
well. The reason we started noticing the truncated/garbage name problems is
that SSL handshake changed (got stricter)
This fix is meant to solve the immediate problem of having
`t_state.hdr_info.server_request` cache not being invalidated after the
escalate plugin called `TSHttpTxnRedirectUrlSet()` to retry the request to a
secondary origin after the primary origin failed.
This code change would invalidate (only invalidate) client request and
server request `HttpHdr` at the same time only during
`HttpSM::redirect_request()`, the caching state of the 2 objects would not
necessarily be kept (or assumed to be) in sync (client request and server
request HttpHdr were not meant to be invariant).
Filed Jira: [TS-4712](https://issues.apache.org/jira/browse/TS-4712) to
look into the `HttpHdr` caching use-cases and verify the HttpHdr caching
functionality.
---
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.
---
