alex1305

I mean that first time file have url https://site.com/cache/m/minify-b1–668946cad3ad601e7d9a5680b14567f1.css?ver=1408781714
The second it will be https://site.com/cache/m/minify-b1–668946cad3ad601e7d9a5680b14567f1.css?ver=1408781730

Looks like i found problem. After flushing cache in BWM. First time when we loading page we get version of minified files that match with version in settings of BWM and those files with right headers even without rules in nginx config (looks like used htaccess rules), but when we loading pahe second time the version of files is changing to version number +16. First time its 1400777 second it will be 1400793 and those files with Cache-Control max-age=0″

Yep i read that info but cant make work headers.
I use friendly url. All files in folder /cache/m/
Thats my nginx conf

server {
		server_name site.com www.site.com;
		listen 000.00.000.0;
		set $root_path /var/www/user/data/www/site.com;
		location ~* ^.+\.(svg|js|css|mp3|ogg|mpe?g|avi|zip|gz|bz2?|rar|swf)$ {
			root $root_path;
			access_log /var/www/nginx-logs/user isp;
			access_log /var/www/httpd-logs/site.com.access.log ;
			error_page 404 = @fallback;
		}
		location / {
			proxy_pass https://000.00.000.0:81;
			proxy_redirect https://000.00.000.0:81/ /;
			proxy_set_header Host $host;
			proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
			proxy_set_header X-Forwarded-Proto $scheme;
			proxy_set_header X-Real-IP $remote_addr;
		}
		location ~* ^/(webstat|awstats|webmail|myadmin|pgadmin)/ {
			proxy_pass https://000.00.000.0:81;
			proxy_redirect https://000.00.000.0:81/ /;
			proxy_set_header Host $host;
			proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
			proxy_set_header X-Forwarded-Proto $scheme;
			proxy_set_header X-Real-IP $remote_addr;
		}
		location @fallback {
			proxy_pass https://000.00.000.0:81;
			proxy_set_header Host $host;
			proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
			proxy_set_header X-Forwarded-Proto $scheme;
			proxy_set_header X-Real-IP $remote_addr;
		}
		# BEGIN BWP Minify Rules
		# BEGIN BWP Minify Headers
		location ~ /cache/m/.*\.(js|css)$ {
			add_header Cache-Control "public, max-age=86400";
			add_header Vary "Accept-Encoding";
		}
		location ~ /cache/m/.*\.js\.gz$ {
			gzip off;
			types {}
			default_type application/x-javascript;
			add_header Cache-Control "public, max-age=86400";
			add_header Content-Encoding gzip;
			add_header Vary "Accept-Encoding";
		}
		location ~ /cache/m/.*\.css\.gz$ {
			gzip off;
			types {}
			default_type text/css;
			add_header Cache-Control "public, max-age=86400";
			add_header Content-Encoding gzip;
			add_header Vary "Accept-Encoding";
		}
		# END BWP Minify Headers
		# END BWP Minify Rules
                location ~* ^.+\.(jpg|jpeg|gif|png|swf|tiff|swf|flv)$ {
		    root $root_path;
		    expires 1y;
		}
		include /usr/local/ispmgr/etc/nginx.inc;

Expires not work too. Maybe there is a error in code you provided? I am not good coder. Sorry.

Dont know why but its not working. My nginx version is 0.7.3 so no support for etag, i remove it. Can i use “expires” and not cache-control? In images i use expires and all work fine.

del

Wow! Its awesome! All work fine. I will donate to you. Your plugin is best from all minify plugins. Thank you!

Ok, thank you!

The problem is that we cant use cache plugins such as super cache and others, because they safe first time we landing

Make a test again and all work fine. Dont know how i got that problem. Big thanks again!

Yes, it was work like you said before. But after last updates plugin filter not work.

Tested on second server same problem. After editing or publish new post, page it rebuilt all cache!

Is it possible with modifying? Can you tell where i can change it if it possible? Thanks!

Yep same think in woocommerce. Welcome messages do not get sent when new user account is created.