[ceph-users] Re: Radogw ignoring HTTP_X_FORWARDED_FOR header

2023-06-26 Thread yosr . kchaou96
Hello, Issue has been found. RGW was not supposed to show the originator's ip in the logs. And my test scenario was not correct. My client was missing some permissions, that's why I get access denied. Yosr ___ ceph-users mailing list -- ceph-users@c

[ceph-users] Re: Radogw ignoring HTTP_X_FORWARDED_FOR header

2023-06-26 Thread yosr . kchaou96
Hello Christian, Thanks for your reply. So running rgw in debug mode shows the correct value of the header HTTP_X_FORWARDED_FOR. And my test scenario is trying to execute a GET request on a bucket on which policies have been applied. So it should accept requests only from a specific ip. And no

[ceph-users] Re: Radogw ignoring HTTP_X_FORWARDED_FOR header

2023-06-26 Thread Christian Rohmann
Hello Yosr, On 26/06/2023 11:41, Yosr Kchaou wrote: We are facing an issue with getting the right value for the header HTTP_X_FORWARDED_FOR when getting client requests. We need this value to do the source ip check validation. [...] Currently, RGW sees that all requests come from 127.0.0.1. So