Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
litespeed_wiki:config:waf:trusted-ip-in-htaccess [2019/02/14 18:51] Jackson Zhang |
litespeed_wiki:config:waf:trusted-ip-in-htaccess [2019/02/14 18:51] (current) Jackson Zhang |
||
|---|---|---|---|
| Line 5: | Line 5: | ||
| You can do so in **LSWS Admin Console > Server > Security > Access Control > Allowed List** by adding a trailing ''T'' to the IP. | You can do so in **LSWS Admin Console > Server > Security > Access Control > Allowed List** by adding a trailing ''T'' to the IP. | ||
| - | Since LSWS 5.4RC1, you may also set a Trusted IP at the virtual host level. Use ''Trusted 1.2.3.4, 5.6.7.8'' (where ''1.2.3.4'' and ''5.6.7.8'' are individual IP addresses) in the virtual host's document root ''.htaccess'' file. This will unblock a blocked IP, and make it trusted for that vhost. Both IPv4 and IPv6 IPs can be used as Trusted IP. When IPv6 IP used, please ensure to use [...] to enclose it. | + | Since LSWS 5.4RC1, you may also set a Trusted IP at the virtual host level. Use ''Trusted 1.2.3.4, 5.6.7.8'' (where ''1.2.3.4'' and ''5.6.7.8'' are individual IP addresses) in the virtual host's document root ''.htaccess'' file. This will unblock a blocked IP, and make it trusted for that vhost. Both IPv4 and IPv6 IPs can be used as Trusted IP. When IPv6 IP used, please ensure to use ''[...]'' to enclose it. |
| Virtual-host-level trusted IPs will bypass LiteSpeed's reCAPTCHA and WordPress brute-force security check features. | Virtual-host-level trusted IPs will bypass LiteSpeed's reCAPTCHA and WordPress brute-force security check features. | ||
| Additionally, since LSWS 5.4RC1, all local IPs and 127.0.0.1, [::1] will be trusted by default. | Additionally, since LSWS 5.4RC1, all local IPs and 127.0.0.1, [::1] will be trusted by default. | ||