Hi @hassanfarid,
- Suppose that you get this JSON body response from middle-service:
{“tenantId”: “123”, “role”: “admin”, “accountId”: “112233”}
If you have the header prefix configured as X-, the new headers are going to be:
X-Tenant-Id: 123
X-Role: admin
X-AccountId: 112233
If you want, you can simulate the whole flow using the docker-composer inside the folder playground.
- I’m not sure if streamdown_injected_headers is the best name for it… do you have a better idea? That’s the new explanation that I added in the README.md
When this option is enabled, the-middleman
will add to the response header all headers added by the-middleman
and by the middle-service.
I use this feature for debugging. It’s just an easy way to see the headers that your destination service are going to receive.
- It’s the same cache implemented by kong: kong.cache
Let me know if something still not clear. Thanks