-
Notifications
You must be signed in to change notification settings - Fork 21
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
Migrate to flask (whois-dev) #20
Comments
I can point AntiCompositeBot's ASNBlock task there. It runs from about 02:30 UTC - 05:00 UTC and 08:13 UTC - 08:30 UTC. The number of WHOIS requests varies between the two runs and over time, but typical volumes range from a few hundred to a thousand requests. |
@AntiCompositeNumber Thank you for testing. Please let me know if you find issues.
I collected the beginnings of down time since June, and it looks like your range does not coincide with it a lot. |
I made a few changes. One surface level change is that parametarized urls ("gateway.py?ip=...") now redirect to REST urls ("w/..."). 0b66298 |
I have been preparing a flask version of the tool inspired by @wiki-ST47 's fork.
https://whois-dev.toolforge.org/ is the new version. I want someone who is running an automated tool to fetch data from this tool to test it. If it goes well, I think I can replace the current version with it.
The current version is CGI-based, which means that a python interpreter launches every time someone tries to access the tool. The flask version runs continuously on a python interpreter. This change might provide better stability and slightly better performance (but not much because the bottleneck is in whois requests which are not cached.)
The text was updated successfully, but these errors were encountered: