gsingh-ds

Well, I understand why this is a problem but our application needs the client IP to work. Using headers to do so is risky that it can be tempered with....

So here is the setup request comes from user then to GraphQL server and then hits out backend server . user -- > graphql --> grpcserver I used your method...

So our service is deployed on AWS App mesh. There is Virtual Gateway and envoy proxy infront of graphql mesh. ref image: https://i.stack.imgur.com/ibY5P.png. I have tried x-forward-for header, seems like...

I think I tried with ['req', 'connection', 'remoteAddress']. I will test your recommendation today. I hope it will work.

Well, It did not work I think because of envoy proxy as a side car, the output of ['req', 'socket', 'remoteAddress'] comes out to be 127.0.0.1. Well, my only hope...

Hello @neild , Thank you for the quick response. Is there a specific reason why this is not supported? Is there anything you can recommend? to solve this issue.

Anyone knows when this will be done?

Any timeline or updates?

I want to set user cookies. Basically wanna send Set-Cookie: {{grpcField}}:{{grpcValue}} to browser

I have quite a bit of experience with Dynamodb and Go. Also we have written a go lib around making working with Dynamo much easier. We were thinking to make...