forked from tornadoweb/tornado
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request tornadoweb#1852 from bdarnell/parse-cookie
httputil: Rewrite cookie parsing
- Loading branch information
Showing
8 changed files
with
173 additions
and
12 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
What's new in Tornado 4.4.2 | ||
=========================== | ||
|
||
Oct 1, 2016 | ||
------------ | ||
|
||
Security fixes | ||
~~~~~~~~~~~~~~ | ||
|
||
* A difference in cookie parsing between Tornado and web browsers | ||
(especially when combined with Google Analytics) could allow an | ||
attacker to set arbitrary cookies and bypass XSRF protection. The | ||
cookie parser has been rewritten to fix this attack. | ||
|
||
Backwards-compatibility notes | ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | ||
|
||
* Cookies containing certain special characters (in particular semicolon | ||
and square brackets) are now parsed differently. | ||
* If the cookie header contains a combination of valid and invalid cookies, | ||
the valid ones will be returned (older versions of Tornado would reject the | ||
entire header for a single invalid cookie). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters