Proxy rewrite (200) on Amplify and IP forwarding

Question

For reasons related to domain usage I am proxying some landing pages from pardot. one of the things I noticed is that the inferred IP of the client in Pardot is always aws server when I use a 200 rewrite.

What headers are transferred? how can i make sure x-forwarded-for is set on rewrites? Also suggestions to how to test this will be appreciated.

Thanks,

Yaron

Accepted Answer

Thank you for reaching out us regarding the above query.

As mentioned in the below GitHub Issue by internal team, as Amplify uses CloudFront  for hosting the application hence, according to the documentation [here](https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/RequestAndResponseBehaviorCustomOrigin.html#request-custom-headers-behavior), Cloudfront removes some request headers while processing the request. You may refer to the headers which are being forwarded by CloudFront.

[+]. GitHub Issue : https://github.com/aws-amplify/amplify-hosting/issues/2316

Further, for performing tests at my end, I used the third party tool - 'https://public.requestbin.com/' for creating a public http endpoint and capturing the requests which are coming from the Amplify application. I could observe that the - 'X-Forwarded-For' header was present in the request (which was my IP). You can also use the above tool for testing at your end.

Having said that, in case you face further challenges, please feel free to open a support case with AWS using the following [link](https://support.console.aws.amazon.com/support/home?#/case/create).

Answer

thanks i did the same, x-forwarded-for exists so its more of a pardot issue. thanks!

Proxy rewrite (200) on Amplify and IP forwarding

Relevant content