From 3e4b6de6ac400eabd112fa71fb6f4c096b6cd991 Mon Sep 17 00:00:00 2001 From: Ram Date: Thu, 27 Nov 2025 11:25:08 +0530 Subject: [PATCH] docs: Add missing AXES_IPWARE_PROXY_ORDER setting documentation --- docs/4_configuration.rst | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/4_configuration.rst b/docs/4_configuration.rst index 50ec604..de060b9 100644 --- a/docs/4_configuration.rst +++ b/docs/4_configuration.rst @@ -109,6 +109,8 @@ following settings to suit your set up to correctly resolve client IP addresses: * ``AXES_IPWARE_META_PRECEDENCE_ORDER``: The names of ``request.META`` attributes as a tuple of strings to check to get the client IP address. Check the Django documentation for header naming conventions. Default: ``IPWARE_META_PRECEDENCE_ORDER`` setting if set, else ``('REMOTE_ADDR', )`` +* ``AXES_IPWARE_PROXY_ORDER``: The order in which to evaluate IP addresses from proxy headers when multiple IPs are present + in the header chain. Must be either ``"left-most"`` or ``"right-most"``. **Default:** ``"left-most"`` .. note:: For reverse proxies or e.g. Heroku, you might also want to fetch IP addresses from a HTTP header such as ``X-Forwarded-For``. To configure this, you can fetch IPs through the ``HTTP_X_FORWARDED_FOR`` key from the ``request.META`` property which contains all the HTTP headers in Django: