Fix Django specific CSRF handling
mallison opened this issue · comments
is it resolved?
This is probably resolved.
You can customise the CSRF header name and cookie name or completely customise headers with a setHeader
callback (in fact you can do whatever you want to the request in setHeaders
-- I should rename that parameter to make it clear).
Do you need to customise? If you can't do what you need to let me know.