summaryrefslogtreecommitdiff
path: root/CHANGES.txt
diff options
context:
space:
mode:
authorBert JW Regeer <bertjw@regeer.org>2016-04-15 16:44:55 -0600
committerBert JW Regeer <bertjw@regeer.org>2016-04-15 16:44:55 -0600
commit1799be9dd8666d10d6b4a04a9b75fc57f8626c6f (patch)
treeefa102960138a09c1f19f16acb30c50af6b5c592 /CHANGES.txt
parentd534c450deeb0163629d7993f6faf12a97b2813c (diff)
downloadpyramid-1799be9dd8666d10d6b4a04a9b75fc57f8626c6f.tar.gz
pyramid-1799be9dd8666d10d6b4a04a9b75fc57f8626c6f.tar.bz2
pyramid-1799be9dd8666d10d6b4a04a9b75fc57f8626c6f.zip
Update CHANGES/whatsnew-1.7 for updated require_csrf
Diffstat (limited to 'CHANGES.txt')
-rw-r--r--CHANGES.txt16
1 files changed, 9 insertions, 7 deletions
diff --git a/CHANGES.txt b/CHANGES.txt
index bc4b1aa79..0a7bdef1a 100644
--- a/CHANGES.txt
+++ b/CHANGES.txt
@@ -25,13 +25,15 @@ Features
``require_csrf=False`` on those views.
See https://github.com/Pylons/pyramid/pull/2413
-- Added a ``require_csrf`` view option which will enforce CSRF checks on POST
- requests. If the CSRF check fails a ``BadCSRFToken`` exception will be
- raised and may be caught by exception views (the default response is a
- ``400 Bad Request``). This option should be used in place of the deprecated
- ``check_csrf`` view predicate which would normally result in unexpected
- ``404 Not Found`` response to the client instead of a catchable exception.
- See https://github.com/Pylons/pyramid/pull/2413
+- Added a ``require_csrf`` view option which will enforce CSRF checks on any
+ request with an unsafe method as defined by RFC2616. If the CSRF check fails
+ a ``BadCSRFToken`` exception will be raised and may be caught by exception
+ views (the default response is a ``400 Bad Request``). This option should be
+ used in place of the deprecated ``check_csrf`` view predicate which would
+ normally result in unexpected ``404 Not Found`` response to the client
+ instead of a catchable exception. See
+ https://github.com/Pylons/pyramid/pull/2413 and
+ https://github.com/Pylons/pyramid/pull/2500
- Pyramid HTTPExceptions will now take into account the best match for the
clients Accept header, and depending on what is requested will return