From 77b25ea4da1aa0bdbc7c6a0ea63085285b66cef7 Mon Sep 17 00:00:00 2001 From: Luke Plant Date: Sat, 23 Jan 2010 23:58:40 +0000 Subject: [PATCH] [1.1.X] Documented backwards incompatibility in 1.1.X branch introduced in r12283 Backport of r12284 from trunk. git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.1.X@12286 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/releases/1.1.2.txt | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/docs/releases/1.1.2.txt b/docs/releases/1.1.2.txt index 4c887ad4a5..36a8051f36 100644 --- a/docs/releases/1.1.2.txt +++ b/docs/releases/1.1.2.txt @@ -32,6 +32,17 @@ status code for the test runner is now 0 for success (no failing tests) and 1 for any number of test failures. If needed, the number of test failures can be found at the end of the test runner's output. +Cookie encoding +--------------- + +To fix bugs with cookies in Internet Explorer, Safari, and possibly other +browsers, our encoding of cookie values was changed so that the characters +comma and semi-colon are treated as non-safe characters, and are therefore +encoded as ``\054`` and ``\073`` respectively. This could produce backwards +incompatibilities, especially if you are storing comma or semi-colon in +cookies and have javascript code that parses and manipulates cookie values +client-side. + One new feature ===============