[Solved] static files expire

${vhostname}.ssl.conf:

Code (Text):

 include /usr/local/nginx/conf/staticfiles.conf;

staticfiles.conf:

Code (Text):

    location ~* \.(js)$ {
        #add_header Pragma public;
        add_header Cache-Control "public, must-revalidate, proxy-revalidate";
        access_log off;
        expires 30d;
        break;
        }

    location ~* \.(css)$ {
        #add_header Pragma public;
        add_header Cache-Control "public, must-revalidate, proxy-revalidate";
        access_log off;
        expires 30d;
        break;
        }

curl:

Code (Text):

no expire and Cache-Control

It seems that the static files go through another location.

---

 

autoprotect for autoptimize before staticfiles?

Code (Text):

location ~ ^/wp-content/cache/autoptimize/(.+/)?(.+)\.(js)$ { allow all; }
location ~ ^/wp-content/cache/autoptimize/(.+/)?(.+)\.(css)$ { allow all; }

 

We have autoprotect include before staticfiles include now. I think that is right. What do you think about this fast patch for autoprotect?

Code (Text):

error_page 418 = @static_file;
location ~ ^/wp-content/cache/autoptimize/(.+/)?(.+)\.(js)$ { allow all; return 418; }

staticfiles.conf

Code (Text):

location @static_file {
        #add_header Pragma public;
        add_header Cache-Control "public, must-revalidate, proxy-revalidate";
        access_log off;
        expires 30d;
        break;
}

need tests

 

better for different redirections

Code (Text):

location ~ ^/wp-content/cache/autoptimize/(.+/)?(.+)\.(js)$ { allow all; error_page 418 = @static_js; return 418; }

or more flexible and stable:

Code (Text):

location ~ ^/wp-content/cache/autoptimize/(.+/)?(.+)\.(js)$ { allow all; include ../../js/*.conf; }

and we do not need to delete the staticfiles.conf include (if the autoprotect include is commented out staticfiles.conf include will work).

 

Autoptimize is a cache plugin and I added new include before autoprotect:

Code (Text):

include /usr/local/nginx/conf/wpincludes/${vhostname}/wpautoptimize_${vhostname}.conf;

and created new conf - wpincludes/${vhostname}/wpautoptimize_${vhostname}.conf

Code (Text):

location ~ /wp-content/cache/autoptimize/ {
    access_log  off;
    error_log   /var/log/nginx/error.log crit;
    deny        all;
    location ~ [^/]+\.(js|css)$ {
        allow all;
        add_header Cache-Control "public, must-revalidate, proxy-revalidate";
        expires max;
        #break;
    }
    location ~ [^/]+\.(php|cgi|pl|php3|php4|php5|php6|phtml|shtml|html)$ {
        allow 127.0.0.1;
        deny all;
    }
}

no bugs now

 

Problem with nginx behavior. You cannot use 2 locations for the file without a redirection. We can use either the autoprotect:

Code (Text):

location ~ ^/wp-content/cache/autoptimize/(.+/)?(.+)\.(js)$

or the staticfiles:

Code (Text):

location ~* \.(js)$

Worked always first location.

I merged autoprotect with staticfiles.

 

I think that you should not touch the autoprotect now. Simply move the autoprotect down after including all caches, and add protection in cache confs if needed.

 

However only one and first regexp will always to work without redirection. Either the autoprotect or staticfiles, that is the question.

 

/wp-content/cache/autoptimize/js/file.js is the correct path

 

Good nginx behavior for autoprotect and included (or not) modules:

Code (Text):

# autoprotect
location ~ /module/file\.js { allow all; }
location ~ /module/file\.css { allow all; }
location ~ /module/bad\.file { deny all; }
location ~ /module/good\.file { allow all; }

# module
location /module/ { # I use prefix and inner locations checks first!
    location ~ /module/.+\.(js|css) { it_is_the_static; } # I allow it if include the module
    # other.files are not interesting for me, autoprotect them.
}

need tests

 

Not strange. Try now. Staticfiles are not works.

 

Yes. It is the best way for autoprotect. Like iptables - deny all now and allow after.

 

Code (Text):

curl -I http://localhost/wp-content/cache/autoptimize/css/test.css