Idea ID: 2874251

Improve AA's HTTPS aka REST API "Rate Limiting Options" parameter to consider X-Forwarded-For Request Header

Elfstone Elfstone
Status : New Idea

As described in the latest AA 6.4 documentation, the current rate limiting feature is virtually useless to organizations of any real size who, being naturally concerned with high availability, place their AA Webservers behind a load-balancer and/or reverse proxy (aka NAM Access Gateways).

Apparently, AA applies this protection mechanism by only examining the TCP layer. It needs to be further extended to examine this HTTPS layer 7 Request Header so that the limits can be applied to the true client IP, and not mistakenly seeing all connections as from all too common load-balancer or reverse proxy addresses in front of AA.