X-Forwarded-For

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements
Please sign in to see details of an important advisory in our Customer Advisories area.

X-Forwarded-For

L1 Bithead

Hello dear, has anyone seen something similar to this: In Primsma-cloud enterprise edition when I create the rule in Defend --> Waas for an environment with kubernetes and using ingress-nginx-controller. In Monitor -->Rules-->Events, in the "IP" field, the ingress-nginx Balancer/reverse proxy address appears instead of the final client's IP address (Real-Ip or the first field of X-Forwarded-For final/endpoint?

2 REPLIES 2

L1 Bithead

Monitor à Events –> WaaS for Containers

HumbertoNeves_1-1709725167807.png

 

HumbertoNeves_2-1709725167816.png

 

 

X-Forwarded-For: 10.244.0.1, 10.244.0.39

 

*X-Forwarded-For: client, proxy

 

not work.

  • 584 Views
  • 2 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!