Make User checks optional and fix a problem posting to Django when CSRF is in use #9
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.
If SCAuthUserCheckURL is set to 'disabled' do not perform the GET to check for a valid user.
This effectively disables the register during logon behaviour for new users.
If a 'csrftoken' cookie is present supply its value in the X-CSRFToken header for POSTs made
during login. This fixes a problem in DJango when the CSRF middleware is enabled and allows
the posted to JSON data to be handled correctly.