You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At https://github.com/pothi/wordpress-nginx/blob/master/globals/wpfc.conf#L28 (written 4 years ago), I have mentioned add_header "Vary" "Cookie"; as an optional setting by commenting it out. But, as things change and as more and more sites use it for requests that shouldn't be cached, I found it to okay and important to enable it by default.
My example configuration/s wouldn't fit every use-case. They are published here as a starting point for anyone to tweak further for their specific scenario. At least, I tweak them before deploying it to every site. For example, if someone uses Cloudflare, Varnish or Fastly, they are likely to include the line set_real_ip_from and real_ip_header. Actually, I am thinking of including Cloudflare support by default, as more and more sites start to use Cloudflare. Also, including Cloudflare support doesn't create any issue for sites that don't use Cloudflare. But, when someone wants to use Fastly, they may have to disable Cloudflare support as both conflict with each other.
Please put forth your further thoughts, if any. I am glad to modify configuration/s to fit more and more users.
You have conflicting settings in the configuration to support WPFC.
Wrong use of Vary header may lead to cache issues especially if CDN is in play.
Please read this post here to understand what I'm talking about:
https://www.fastly.com/blog/best-practices-using-vary-header
The text was updated successfully, but these errors were encountered: