[Plugin: W3 Total Cache] W3TC Rules with NGINX Potentially Causing Interminent Infinite Loops
-
Frederick,
We have three high traffic sites up right now running NGINX as a reverse proxy to Apache. Our W3TC rules are in NGINX.CONF and the only rules in Apache.Conf (Static config) are standard WordPress re-write rules. We used the default rules generated for W3TC. Our selections are page cache = disk enhanced, min = disk, no CDN, opcache = APC, Browser Cache on . All other settings within are default.
From our point of view, performance and memory consumption is bad ass. However, Pingdom has started hiccuping about every 30 minutes with reports of infinite 301 redirection loops.
We are working through our conf files to make sure we are not causing it but wanted to let you know in the event there was a bug with your NGINX support. Our conf starts with the following and then simply has your re-writes per your output
server {
listen 80;
access_log /var/log/nginx/ourblog.com.access.log;
server_name ourblog.com https://www.ourblog.com;
root /var/www/ourblog.com;[W3TC ENTRIES]
followed by
location / {
#root /var/www/ourblog.com;
index index.html index.htm index.php;
error_page 404 = @dynamic;
}location ~ \.php$ {
proxy_pass https://localhost:8080;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
}location @dynamic {
location @dynamic {
proxy_pass https://localhost:8080;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header Host $host;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
}location ~ /\.ht {
deny all;
}
}Any insight you can provide is much appreciated.
Derick
- The topic ‘[Plugin: W3 Total Cache] W3TC Rules with NGINX Potentially Causing Interminent Infinite Loops’ is closed to new replies.
