02-17-2023 04:26 PM
Trying to implement this.
Azure Web Application Gateway is in the front, acting as proxy. I can see packet captures for port 80 x-forward for is included
But i don't see xff in traffic logs, and matching the url accessed shows traffic from Azure Gateways internal backend IP and not from the original client IP in XFF.
How ever I don't see IP under XFF traffic logs as source ip
Also i tried adding source ip to be blocked to test, and could not get it to work
02-20-2023 01:12 AM
Hello, I suspect that because also the port is included it causes issues. Try to have an HTTP header that contains just one IP address without a port :
https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClIVCA0
02-20-2023 01:12 AM
Hello, I suspect that because also the port is included it causes issues. Try to have an HTTP header that contains just one IP address without a port :
https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClIVCA0
02-21-2023 08:58 AM
Thanks @nikoolayy1
Rewriting HTTP header on Application Gateway to remove port information made it work.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
