#37107: Request META key `REMOTE_ADDR` not set anywhere in wsgi applications
-------------------------------------+-------------------------------------
Reporter: Rami Boutassghount | Owner: (none)
Type: Uncategorized | Status: new
Component: Core (Other) | Version: 6.0
Severity: Normal | Resolution:
Keywords: REMOTE_ADDR, | Triage Stage:
WSGIRequest, HttpRequest, META | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Richard Autry):
It's unlikely that `REMOTE_ADDR` would be used if your application sits
behind a reverse proxy (i.e. `nginx`), and `HTTP_X_FORWARDED_FOR` would be
the actual header you want to use.
`REMOTE_ADDR` is a server var and only useful if there is a direct (TCP)
connection. This is not a `Django` bug or mistake in the docs.
See https://docs.oracle.com/html/E10726_01/c06_core_ref200.htm
--
Ticket URL: <https://code.djangoproject.com/ticket/37107#comment:1>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019e42b40b93-a1b0510e-f305-4c3a-abba-a12238972e07-000000%40eu-central-1.amazonses.com.
