Hello,
Configure WAF : enable IP workarounds when using Siteground dynamic cache.
I'm using Siteground dynamic cache, but no CDN
Should I use "Enable IP workarounds" with param YES or AUTO? Perhaps NO?
#34526 Enable IP workarounds when using Siteground dynamic cache?
Posted in ‘Admin Tools for Joomla! 4 & 5’
This is a public ticket
Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Environment Information
Joomla! version
n/a
PHP version
n/a
Admin Tools version
n/a
Latest post by lesyeux on Friday, 12 February 2021 04:14 CST
Friday, 12 February 2021 00:50 CST
nicholas
Akeeba Staff
Manager
If I recall correctly, their "dynamic cache" refers to a Varnish caching proxy installation in front of your site. If this is the case then yes, you need to enable IP workarounds.
Contact their support and ask them what is the technology behind this generically and deceptively named feature. If it's a caching proxy you need to enable IP workarounds. If it's memcached or something similar you don't need to enable IP workarounds.
If unsure, leave it disabled. If someone getting blocked results in everybody else getting blocked then you need to enable the IP workarounds feature.
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!
Friday, 12 February 2021 02:20 CST
lesyeux
Hi,
The technology behind "Dynamic Cache" would be more precisely "NGINX-powered Dynamic Cache".
I found this official information about this caching method:
https://www.nginx.com/blog/benefits-of-microcaching-nginx/
Caching, even at the reverse proxy/load balancer level, can greatly improve performance. (…)
NGINX is commonly deployed as a reverse proxy or load balancer in an application stack and has a full set of caching features. (…)
Only two directives are needed to enable basic caching: proxy_cache_path and proxy_cache. The proxy_cache_path directive sets the path and configuration of the cache, and the proxy_cache directive activates it.
And so it is indeed a caching proxy. Or am I wrong?
Friday, 12 February 2021 03:56 CST
nicholas
Akeeba Staff
Manager
Assuming it's NginX in front of Apache, per the article you quoted, and not something that SiteGround made up: NginX HOULD be configured to forward the correct IP to Apache. In this case you wouldn't need the Enable IP Workarounds. As I said, you can just leave it disabled for now. If someone getting blocked results in everybody else getting blocked then and only then do you need to enable the IP workarounds feature.
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!
Friday, 12 February 2021 04:14 CST
lesyeux
Thanks a lot.