Does maas understand the x-forwarded-for header and use it for logging?

Docs
1

When using maas in an HA mode behind haproxy, the maas region controllers now only report the haproxy IP, Is maas capable of understanding the x-forwarded-for header and logging the real client’s address?

2021-04-19 15:38:54 regiond: [info] 10.40.148.66 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
2021-04-19 15:38:55 regiond: [info] 10.40.148.66 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
2021-04-19 15:38:56 regiond: [info] 10.40.148.66 GET /MAAS/rpc/ HTTP/1.1 --> 200 OK (referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)

10.40.148.66 is the IP of the haproxy instance

2

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.