Conversation
|
Any news on this? The most desired feature at the moment. |
|
Just curious how |
|
In our case, our private server has a global IP address, but it is closed from the Internet with firewall and access allowed only inside the same network. |
|
Hmm, I don't feel comfortable adding this feature because of your specific network configuration. I would recommend doing The Right Thing (tm) and assigning that server a non-routable subnet IP address. |
|
I don't want to argue. But The Right Thing looks a little bit subjective in this case. |
Ignoring internal sources is already supported with a fixed IP whitelist, but this doesn't support cases where an internal source doesn't fall within those IPs blocks. This change allows specific hostnames to be ignored.
cb7e5b3 to
809f814
Compare
Ignoring internal sources is already supported with a fixed IP whitelist, but this doesn't support cases where an internal source doesn't fall within those IPs blocks. This change allows specific hostnames to be ignored.
Example usage:
This change co-opts
--ignorefor simplicity, but not sure if it's better to give it its own option.