On 9/20/07, Craig Ogg <[EMAIL PROTECTED]> wrote: > > On 9/20/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote: > > Django's SetRemoteAddrFromForwardedFor middleware used to take the > > *first* item in the X-F-F header, but after > > http://code.djangoproject.com/ticket/3872 was filed we changed it to > > take the *last* IP. > > > > That ticket use this article as a reference: > > http://bob.pythonmac.org/archives/2005/09/23/apache-x-forwarded-for-caveat/ > > as its source for information. That article is about reverse proxying > rather than proxying
The middleware is about reverse proxying too. According to the doctests: "[...] if you're not behind a reverse proxy that sets HTTP_X_FORWARDED_FOR automatically, do not use this middleware" -- Leo Soto M. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
