#3872: Bug in SetRemoteAddrFromForwardedFor middleware
------------------------------+---------------------------------------------
Reporter: Simon Willison | Owner: gregorth
Status: reopened | Component: Core framework
Version: SVN | Resolution:
Keywords: middleware | Stage: Ready for checkin
Has_patch: 1 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
------------------------------+---------------------------------------------
Changes (by Chris Bennett <[EMAIL PROTECTED]>):
* status: closed => reopened
* resolution: fixed =>
Comment:
Wait a minute... client IS the first IP listed.
http://en.wikipedia.org/wiki/X-Forwarded-For
And I'm looking at request on a machine being proxied by Apache right now:
HTTP_X_FORWARDED_FOR: 66.162.32.x, 127.0.0.1
Also, some reverse proxies may pass X-Forwarded-For and its capitalization
variants in place of HTTP_X_FORWARDED_FOR.
Though, in either case, the origin client is clearly first. Revert?
--
Ticket URL: <http://code.djangoproject.com/ticket/3872#comment:6>
Django Code <http://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 post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
