Support for dropping port out of x-forwarded-for header
I've seen some compatibility issues with the x-forwarded-for header as it comes in on the format IP:Port rather than just IP. It would be useful to be able to adjust this header to just provide IP without the port. I think this should be adjustable, so IP:Port or just IP being available options rather than just one or the other.
This would help x-forwarded-for being easy to parse on systems that only expect the IP to be sent through.
This can now be accomplished using the Header Rewrite capability (https://azure.microsoft.com/en-us/blog/rewrite-http-headers-with-azure-application-gateway) available with Application Gateway’s V2 SKU. Please see details here:
Please remove the Port Information or/and make it configurable via a setting in the portal.
This would be a great feature. Our CMS's lack of parsing out the port number has been holding back our AG implementation.
Andres Barcenas commented
+10000 please remove the port.
We have problems with TYPO3 behind the gateway, getting the right IP address of the user. Because of the unknown format the CMS has problems with parsing it.
Need that too.
We are currently having this issue with Sitecore. Please provide this option, thank you!