-
-
Notifications
You must be signed in to change notification settings - Fork 53
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
Way to add subnets on ip addresses to ignore #70
Comments
@davidgomezcol as documentation says:
So you just need to "prepare" your url for regex usage: MAINTENANCE_MODE_IGNORE_URLS = ('192\.168\.0\.0\/32',) |
Great! thank you very much! didn't mean to put this as a bug, but github didn't give me another option. Thank you for you quick reply.. |
Don't worry! |
Hello!.. I'm adding my ip addresses like this.. but it doesn't seem to work.. i'm still having 503's after this.. and there's a bunch of them.. i'm just sharing you a little.. there's about of 200 ip addresses that i need to add there.. I tested both ways and is not working for me... --- > MAINTENANCE_MODE_IGNORE_URLS |
Sorry, but there is some confusion here:
So, in your case you should add ip-addresses to |
I'm using django-ipware to get the user ip address.. the problem is that i have is with this kind of ip addresses 23.64.0.0/14 that could be a bunch of them, so if django-ipware grabs the ip address for example 23.67.255.255 that would be in the list of ip address from 23.64.0.0/14. I thought that probably this could have an internal function that handles that kind of situation, where can be a added this way.. i have a large list of ip addresses that i need to add like that.. |
You should write your own function wrapping ipware. |
Python version
3.8
Django version
1.11
Package version
0.14.0
Current behavior (bug description)
Is there a way to add the subnets to the ip addresses to ignore when maintenance mode is active?
to something like this? because i tried this way and it's not working for me:
MAINTENANCE_MODE_IGNORE_URLS = ('192.168.0.0/32',)
Expected behavior
192.168.0.0/32
The text was updated successfully, but these errors were encountered: