Disappearing Response Header

[diegoBlaylock]

I am encountering a strange bug where an app resource stemming from a Kubernetes resource is attempting to send the header x-accel-buffering: no, however when the app runs in production and that response travels through teleport, the header is never seen by the client.

Does teleport delete response headers? If so is there any configuration to allow these headers to pass through?

Extra info:

I have a Kubernetes cluster setup with a teleport-cluster and teleport-kube-agent helm charts. Teleport itself is behind a L7 load balancer(LB), which I have successfully tested directly with the application (no teleport proxy, just LB and app). It is unlikely to be the problem, but possible too. This question is really just to see if teleport may have anything to do with it.

[diegoBlaylock]

No response so I will close this discussion.