django1/django/middleware
Jacob Kaplan-Moss d78cf61c99 BACKWARDS-INCOMPATIBLE CHANGE: Removed SetRemoteAddrFromForwardedFor middleware.
In a nutshell, it's been demonstrated that this middleware can never be made reliable enough for general-purpose use, and that (despite documentation to the contrary) its inclusion in Django may lead application developers to assume that the value of ``REMOTE_ADDR`` is "safe" or in some way reliable as a source of authentication. So it's gone.

See the Django 1.1 release notes for full details, as well as upgrade instructions.

git-svn-id: http://code.djangoproject.com/svn/django/trunk@11363 bcc190cf-cafb-0310-a4f2-bffc1f526a37
2009-07-29 05:35:51 +00:00
..
__init__.py Imported Django from private SVN repository (created from r. 8825) 2005-07-13 01:25:57 +00:00
cache.py Fixed #9221 -- Small optimisation to caching middleware handling. 2008-09-30 03:58:09 +00:00
common.py Fixed #9199 -- We were erroneously only prepending "www" to the domain if we 2008-10-07 08:22:50 +00:00
doc.py Fixed #2747 -- Make X-Headers work for staff members. Admins with dyanmic IP 2006-09-22 03:17:28 +00:00
gzip.py Fixed #10630 -- Be even more conservative in GZipMiddleware for IE. 2009-04-12 04:14:23 +00:00
http.py BACKWARDS-INCOMPATIBLE CHANGE: Removed SetRemoteAddrFromForwardedFor middleware. 2009-07-29 05:35:51 +00:00
locale.py Fixed #8121 -- Don't override the Content-Language HTTP header in the locale 2008-08-09 15:04:45 +00:00
transaction.py Second half of little cleanup tweaks suggested by pyflakes. 2006-07-21 20:39:17 +00:00