Request body missing in Rails app behind Envoy Gateway – Possible Envoy config issue? #6454
Unanswered
mohammed-rahib
asked this question in
Q&A
Replies: 1 comment 3 replies
-
you can check with |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm using Envoy Gateway in my EKS cluster, and I'm facing an issue where the request body is missing in our Rails app when receiving webhooks from a third-party client.
Setup:
I have a custom EnvoyProxy resource.
My GatewayClass points to this EnvoyProxy.
A Gateway is defined using that class.
I have a Service and an HTTPRoute routing traffic to a Rails application pod.
The third-party service is sending webhook POST requests, and they claim that the request body is being sent properly. However, when it reaches our Rails app, the body is empty.
NB:- When we replicated their request using curl, the body was received correctly.
My questions:
Could this be a misconfiguration in Envoy Gateway that strips or drops the request body?
Is there a way to log the request body in the Envoy Proxy pod logs to verify if the body is received at the proxy level?
Right now, I'm seeing only the default Envoy access logs, as shown here:
https://gateway.envoyproxy.io/latest/tasks/observability/proxy-accesslog/#default-access-log
Any guidance on:
Possible misconfigurations to check?
How to enable full request/response body logging (even temporarily for debugging)?
Beta Was this translation helpful? Give feedback.
All reactions