Ah yeah. Wondered about that. It seems like though the shun is usually behind the apache request right now? I guess in a heavy load situation maybe that wouldn't be the case though?mikeshinn wrote:No worries, glad I could help.
The idea behind the port 30000 and https was to redirect to a port/listener that maybe was always open, so even if you shunned the badguy they would still get the page explaining why.
Actually now that I look. the address im going through is actually on cloudflare so access is still allowed even if they get blocked. They just won't be able to do any requests that require my server to kick in. I guess that works.