Add ASP.NET ValidateAntiForgeryToken feature #2206
Open
Conversation
This file contains hidden or 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
Jtable ajax calls to controler actions marked with [ValidateAntiForgeryToken] may not work because Antiforgery checks the request header for an antiforgery token which is then compared with the cookies token. If they don't match or the token is missing, the server responds with error 400. All this is to prevent Cross-Site Request Forgery (CSRF) Attacks. This fix attempts to manage this by adding a security option where a antiforgerytoken can be passed, this is then added to the ajax call header for server side validation. usage would be like:
var token = 'gettokenvalue'
$('#CategoriesContainer').jtable(
{
title: 'Categories',
paging: false,
sorting: false,
security:
{
antiforgerytoken: token
},
actions: {----------
brunomacharia
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Jtable ajax calls to controler actions marked with [ValidateAntiForgeryToken] may not work because Antiforgery checks the request header for an antiforgery token which is then compared with the cookies token. If they don't match or the token is missing, the server responds with error 400. All this is to prevent Cross-Site Request Forgery (CSRF) Attacks. This fix attempts to manage this by adding a security option where a antiforgerytoken can be passed, this is then added to the ajax call header for server side validation. usage would be like:
var token = 'gettokenvalue'
$('#CategoriesContainer').jtable(
{
title: 'Categories',
paging: false,
sorting: false,
security: {
antiforgerytoken: token
},
actions: {----------