Changes between Version 125 and Version 126 of BackwardsIncompatibleChanges

Timestamp:

Sep 14, 2007, 2:39:02 AM (17 years ago)

Author:

Malcolm Tredinnick

Comment:

Added set-language change.

BackwardsIncompatibleChanges

@@ -37 +37 @@
  * [6057] Sept. 6, 2007: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#archive_yeargenericviewnolongerperformsanorder_byonthepassedqueryset archive_year generic view no longer performs an order_by() on the passed queryset]
  * [6075] Sept. 9, 2007: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#django-admin.pyandmanage.pynowrequiresubcommandstoprecedeoptions django-admin.py and manage.py now require subcommands to precede options]
-
+ * [6177] Sept. 14, 2007: [http://code.djangoproject.com/wiki/BackwardsIncompatibleChanges#django.views.i18n.set_languagerequiresaPOSTrequest django.views.i18n.set-language requires a POST request]
 
 == Database constraint names changed ==
@@ -374 +374 @@
 Now, options must come after the subcommand:
 {{{django-admin.py runserver --settings=foo.bar}}}
+
+== django.views.i18n.set_language requires a POST request ==
+
+In [6177], the {{{set_language()}}} view was changed to only change the caller's locale if called as a POST request. Previously, a GET request was used. The old behaviour meant that state (the locale used to display the site) could be changed by a GET request, which is against the HTTP specification's recommendations.
+
+Code calling this view must ensure that a POST request is now made, instead of a GET. This means you can no longer use a link to access the view, but must use a form submission of some kind (e.g. a button).