Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Ambassador overwrites value of x-request-id header.
See original GitHub issueDescribe the bug Ambassador overwrites value of x-request-id header.
To Reproduce We use ambassador as our API gateway (with default configuration) in GKE. A Javascript frontend sends an x-request-id header with UUID as a value for tracing capabilities.
Expected behavior The value of x-request-id header that was sent from the frontend to the backend via Ambassador shouldn’t be changed.
Versions (please complete the following information):
- Ambassador: 0.85.0
- GKE 1.14.7
Additional context
Since the default behaviour of envoy is to overwrite x-request-id, there is an option to override this behaviour by setting preserve_external_request_id: true when configuring envoy using config.yaml.
The question is how to do this in Ambassador using ambassador.yaml? I believe that it’s a one-liner solution but this option isn’t documented anywhere.
gz#950
Issue Analytics
- State:
- Created 4 years ago
- Reactions:7
- Comments:15 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@eddy-curv Ping!! Can you check with the new ambassador version?
Thanks @prakharjoshi, really hope that the IR module flow will be fixed, we would really like to use that preserve_external_request_id ability.