Here's an odd one. I have a transform that caches the untransformed response, so that way I perform the transformation for each subsequent cache hit of that document. This works well enough, until my plugin is in a cluster. When in a cluster, if the cached document is peer fetched the response headers returned to the client are corrupted. If it is not peer fetched, it works fine.
I've done many tests with a single node, and in a cluster, and am convinced being in the cluster is the key factor to this bad behavior. I am at a loss. Why does being part of a cluster cause this? Should I be handling response headers differently?
