Please sign in to comment.
Updating cookie format to be quoted to follow the RFC
Summary: We were including the '=' sign in our cookie. This is not valid according to the RFC unless the value is quoted. This breaking change adds those quotes to our cookie value. This was reported on Github with relation to Apache Tomcat which follows the RFC: http://github.com/facebook/connect-js/issues/#issue/2/comment/77244 This is the first breaking change since the initial alpha release. I've created a changelog.md file and linked it from the readme. Reviewed By: lshepard CC:email@example.com Test Plan: Ran tests. DiffCamp Revision: 75467
- Loading branch information...
Showing with 25 additions and 6 deletions.
|@@ -0,0 +1,13 @@|
|+*Date*: 20th November, 2009|
|+We were including the '=' sign in the cookie value which although works on many|
|+servers, is not actually valid accoring to [RFC2965][CookieRFC]. The correct|
|+way to include the '=' character is by having the cookie value be quoted.|
|+The result is that you will need to update your server side logic for parsing|
|+the Cookie to handle the quotes if needed.|