Add support for automatic CSRF token injection #188
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.
Closes #36
Support secure CSRF protection for htmx-driven requests across all relevant HTTP methods.
Changes:
HtmxAttributeProcessorto make it easier to extend.HtmxCsrfAttributeProcessor(with@since 5.1.0annotation) to handle CSRF token injection.HtmxDialectto associate the new processor withpost,put,patch, anddeleteattributes.README.md.Implementation Notes:
hx-valsto send the CSRF token. However, DELETE requests expose the token in query parameters.hx-headers, which is more secure and aligns with htmx recommendation.