Author: lukeplant
Date: 2009-03-23 11:37:25 -0500 (Mon, 23 Mar 2009)
New Revision: 10120
Modified:
django/trunk/docs/releases/1.1-alpha-1.txt
Log:
Removed erroneous changes to 1.1 alpha 1 release notes.
Modified: django/trunk/docs/releases/1.1-alpha-1.txt
===================================================================
--- django/trunk/docs/releases/1.1-alpha-1.txt 2009-03-23 09:42:51 UTC (rev
10119)
+++ django/trunk/docs/releases/1.1-alpha-1.txt 2009-03-23 16:37:25 UTC (rev
10120)
@@ -74,14 +74,8 @@
``CsrfMiddleware`` class (which does both) remains for
backwards-compatibility, but using the split classes is now recommended in
order to allow fine-grained control of when and where the CSRF processing
- takes place. Decorators are provided for selectively turning it off for
- certain views.
+ takes place.
- Also, these middleware are now enabled by default when creating new projects.
- It is recommended to add these middleware, if not already present, to
existing
- projects, to provide protection for the admin (which has no other CSRF
- protection) and other apps.
-
* :func:`~django.core.urlresolvers.reverse` and code which uses it (e.g., the
``{% url %}`` template tag) now works with URLs in Django's administrative
site, provided that the admin URLs are set up via
``include(admin.site.urls)``
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
