This handler adds a CSRF token to requests which mutate state. In order change the state a (XSRF-TOKEN) cookie is set with a unique token, that is expected to be sent back in a (X-XSRF-TOKEN) header.
The behavior is to check the request body header and cookie for validity.
This Handler requires session support, thus should be added somewhere below Session and Body handlers.
no subtypes hierarchy
|Attributes inherited from: |
Set the cookie name. By default XSRF-TOKEN is used as it is the expected name by AngularJS however other frameworks might use other names.
Set the cookie path. By default / is used.
Set the header name. By default X-XSRF-TOKEN is used as it is the expected name by AngularJS however other frameworks might use other names.
Should the handler give warning messages if this handler is used in other than https protocols?
Set the body returned by the handler when the XSRF token is missing or invalid.
Set the timeout for tokens generated by the handler, by default it uses the default from the session handler.
|Methods inherited from: |