From 7e73dc76de0e4558c2f2db05bd7289d53fdfb4c0 Mon Sep 17 00:00:00 2001 From: Bart Ducheyne Date: Fri, 15 Jan 2016 10:34:46 +0100 Subject: [PATCH] intention was renamed to csrf_token_id The parameter intention was renamed to csrf_token_id and not yet updated in the documentation. --- cookbook/security/csrf_in_login_form.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/cookbook/security/csrf_in_login_form.rst b/cookbook/security/csrf_in_login_form.rst index 5853bbec647..84c71242fca 100644 --- a/cookbook/security/csrf_in_login_form.rst +++ b/cookbook/security/csrf_in_login_form.rst @@ -124,7 +124,7 @@ After this, you have protected your login form against CSRF attacks. .. tip:: You can change the name of the field by setting ``csrf_parameter`` and change - the token ID by setting ``intention`` in your configuration: + the token ID by setting ``csrf_token_id`` in your configuration: .. configuration-block:: @@ -140,7 +140,7 @@ After this, you have protected your login form against CSRF attacks. form_login: # ... csrf_parameter: _csrf_security_token - intention: a_private_string + csrf_token_id: a_private_string .. code-block:: xml @@ -158,7 +158,7 @@ After this, you have protected your login form against CSRF attacks. @@ -176,7 +176,7 @@ After this, you have protected your login form against CSRF attacks. 'form_login' => array( // ... 'csrf_parameter' => '_csrf_security_token', - 'intention' => 'a_private_string', + 'csrf_token_id' => 'a_private_string', ), ), ),