This repository has been archived by the owner on Aug 23, 2020. It is now read-only.
Use classed based views for Django 1.11 #82
Conversation
This file contains 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Fixes #80 for Django 1.11. For other versions of django a fix is needed in
password_reset_confirm.htmlto add the tag<meta name="referrer" content="never">andrel="noreferrer"should be added to the anchor tag inpassword_reset_email.html. I didn't see either of these templates in the repository, so it may be best to just warn users of the issue of potentially leaking the reset token through theReferrerheader.