3 ms·
There’s no cookie so I assume you’re restricting it to one entry per day based on IP. Could somebody ruin the whole thing by flooding the server with requests w
by codyrobbins 16y ago
There’s no cookie so I assume you’re restricting it to one entry per day based on IP. Could somebody ruin the whole thing by flooding the server with requests with spoofed IP addresses?
- Liron 16y agoI have my own uniqueness detection heuristic. The short answer is yes, but then I'll invalidate the win and add a CAPTCHA.
- webignition 16y agoThere's no per-IP restriction that I could see. I tried 4 different browsers on the same machine and each was able to try. I tried with new browser sessions, with HTTP cookies and Flash cookies cleared all to no avail. I even tried: curl -d "" http://www.areyou1in1000000.com/ http://www.areyou1in1000000.com/ There's either some really good or really bad duplicate entry prevention going on.
- andreyf 16y agoThere's either some really good or really bad duplicate entry prevention going on. Probably IP + User Agent.
- deleted 16y ago[deleted]
- MichaelGG 16y agoIf someone in a position to fully establish TCP connections with spoofed IPs wanted to ruin something, I'd think they'd find something a lot more interesting to do...