New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle csrf stored in sessions #111
Conversation
This allow to use CSRF_USE_SESSIONS = True which store crsf token in session instead of cookies.tting CSRF_USE_SESSIONS = True. It checks if csrf token found in cookies otherwise try to get csrf token in session.
Use full modification ! |
It would be nice to have this implemented :) |
Yes for sure, this feature will be very useful when we change the method to handle the CSRF token.
There is surely a way "more pretty" by giving the mode used by Django to handle the token from the The fact that travis-ci job crash is not to be considered because |
In that case django has to parse the .js file as template before serving it, thats not pretty either. |
But why there is this bac787b#diff-fd2204ac82e19c15973d9a6bb1452905R126 line left in the code? It should be deleted. |
Clearly a mistake indeed, i overlooked it in the diff. Can you correct or comment on this @TheBuky |
Also, please update PR to latest code from github. There is already a fix for travis error. |
My bad, what a shameful newbie mistake... |
@adi- Can you be more precise about the PR? |
* Handle csrf stored in sessions This allow to use CSRF_USE_SESSIONS = True which store crsf token in session instead of cookies.tting CSRF_USE_SESSIONS = True. It checks if csrf token found in cookies otherwise try to get csrf token in session. * Remove useless line
This was helpful |
This allow to use CSRF_USE_SESSIONS = True which store crsf token in session instead of cookies.
It checks if csrf token found in cookies otherwise try to get csrf token in session.