Carl Zogheib

Same issue in `2.0.0` ``` Cannot read property 'tap' of undefined ```

Additionally it seems like the [Vault Proxy documentation on request uniqueness](https://developer.hashicorp.com/vault/docs/agent-and-proxy/proxy/caching#request-uniqueness) describes the implementation of the cache key as: > In order to detect repeat requests and return cached responses,...

Thanks @VioletHynes for your quick triaging and confirmation of this bug! > For static secrets, we do not cache based on a key formed by the request body/headers like we...

Thank you so much @VioletHynes - looking forward to that! Are you able to specify whether we will need both the remote Vault Server + Vault Proxy to consume the...

Hey @VioletHynes - thank you again for addressing the reported issue! This patch has however changed the behavior of the Proxy in a way we didn't expect and likely puts...

Thanks again @VioletHynes - we are seeing this for requests both with and without a specific version - eg: ```shell $ vault kv get -namespace {namespace} -mount {kvv2_name} {secret_path} ......

That makes total sense, thanks! So it's a CLI-driven request, I can validate that I don't see this when requesting with `curl`: ```shell curl -k -X GET http://127.0.0.1:8200/v1/{kvv2_name}/data/{secret_path} --header "X-Vault-Namespace:...

+1 to this

We have worked around this and currently have Vault Agent / Proxy set up with persistent caching in "kubernetes" mode without actually running in Kubernetes. "type = kubernetes" really only...