Merged
Conversation
adamchainz
force-pushed
the
user_ip
branch
3 times, most recently
from
6935ceb to
12faa09
Compare
* Inline the `RemoteIp` class into Django - it was well intentioned but too Django specific since headers work differently on each web framework * Extract the common parts of tracking to functions in Django, which adds `user_ip` and `path` tracking to Django < 1.10 where it was missing * Add user IP tracking on Flask
This file contains hidden or 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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
RemoteIpclass into Django - it was well intentioned but too Django specific since headers work differently on each web frameworkuser_ipandpathtracking to Django < 1.10 where it was missing