Re:Caddy 0.9 Released with All New Core
by vesak on Tuesday July 19, 2016 @04:57AM
(#12120646)
Wouldn't you normally want to do ip filtering on a lower level?
[ Parent
| on HN ]
Sure, if you want to serve TCP reset / ICMP port-unreachable to blocked users, then yes - iptables or external firewall is a more natural way to do it.
But what if you want to serve different content to "blocked" users? i.e. login page, "we're sorry" page, redirect to read-only version of the site, reminder to connect to office VPN, anything like that...
Another example - more than one site on the same (server) IP, and only part of them are (client) IP-restricted.
Re:Caddy 0.9 Released with All New Core
by pritambaral on Tuesday July 19, 2016 @10:36AM
(#12122020)
Considering that firewalls are the best tools to "filter" by IP ranges, I'd suggest this "hack": Reroute the "blocked" packets (my favourite method is DNAT with iptables) to a different webserver which only serves the special pages.