Why wont It Optimize Its Own Script

afternoon @bformhals19;
expiration values for static files are set by your webserver(s), either change config there (and if on Apache check for “rogue” entries in /.htaccess and /wp-content/.htaccess) or try if disabling the “serve as static files” option on AO’s settings-screen helps.

hope this clarifies,
frank

The css also has insecure resources for the plugin that create bad SSL errors

Insecure URL: https://res.cloudinary.com/di7ipdger/image/upload/v1509603878/banner_1_sr5rqk.jpg
Found in: https://multimediaconsultinggroup.com/wp-content/cache/autoptimize/css/autoptimize_2ecf867599e495e87867f494830d9c1c.css

I dont even see this in the settings
disabling the “serve as static files” option on AO’s settings-screen helps.

As for the css I just mentioned I corrected that myself by fixing your css. Im lost on fixing the other items. Just seems like if this is used to optimize the site it shouldnt do what it is doing.

Is it safe to put my access file here. Also, if you update the plugin will my css fixinf the error go back to the way it was?

regarding the http-link; that actually originates from view-source:https://multimediaconsultinggroup.com/wp-content/themes/pearl/assets/css/app.css?ver=1.6 @bformhals19, you’ll have to change it there. editing AO’ed CSS (or JS) will never persist.

hmm, shouldnt your css be changed accordingly also? The error will just continue wont it?

all you have to do is clear AO’s cache and all will be fine @bformhals19 ??

regarding

I dont even see this in the settings

make sure to click the “show advanced settings”-button near the top-right-ish corner of the AO-settings-screen.

On the YSlow score there are come css from autoptimize how can these be added to expiration headers

https://multimediaconsultinggroup.com/wp-content/cache/autoptimize/css/autoptimize_c1820dc97e36ce5eb3956e851d01f6ce.css
https://multimediaconsultinggroup.com/wp-content/cache/autoptimize/css/autoptimize_501cb611d5d3752206458fbc9589dfac.css
https://fonts.googleapis.com/css?family=Open+Sans%3A300%2C400%2C400i%2C500%2C600%2C700%2C800%2C900%7CMontserrat%3A300%2C400%2C400i%2C500%2C600%2C700%2C800%2C900&ver=1.6
https://fonts.googleapis.com/css?family=Open+Sans:400
https://multimediaconsultinggroup.com/wp-content/cache/autoptimize/js/autoptimize_0ca4e29e26b80c77b9f05ae3b0f6bf8c.js
https://pixel.wp.com/g.gif?v=ext&j=1%3A5.5&blog=39292924&post=1713&tz=-5&srv=multimediaconsultinggroup.com&host=multimediaconsultinggroup.com&ref=&rand=0.45419606446330363
https://multimediaconsultinggroup.com/wp-includes/js/wp-emoji-release.min.js?ver=4.8.3
https://multimediaconsultinggroup.com/wp-content/plugins/revslider/public/assets/js/extensions/revolution.extension.slideanims.min.js?version=5.4.6
https://multimediaconsultinggroup.com/wp-content/plugins/revslider/public/assets/js/extensions/revolution.extension.layeranimation.min.js?version=5.4.6

Expiration values for static files are set by your webserver(s), either change config there or try if disabling the “serve as static files” option on AO’s settings-screen (make sure “advanced settings” are shown) helps.

frank

Sorry Ive tried everything all static resources are good except the ones associated with this plugin. An optimizing plugin we should be able to fix this??? Help

https://multimediaconsultinggroup.com/wp-content/cache/autoptimize/css/autoptimize_046821c0aee3af4b893a6206cc3e45df.css

https://multimediaconsultinggroup.com/wp-content/cache/autoptimize/css/autoptimize_b7b3e4f75914a8c601cdc1ada1567ba2.css

https://multimediaconsultinggroup.com/wp-content/cache/autoptimize/js/autoptimize_c8bda905cc7f4c118609ee1d0b2c8050.js

Cache-Control: max-age=3, must-revalidate, public, immutable

is typically a remnant of WP Super Cache, probably in wp-content/cache/.htaccess @bformhals19, AO itself sets the max-age to a _very_ high value, but cannot override what is probably WP Super Cache’s rule, so you’ll have to find and remove the reason for that max-age=3.

No the problem the cache-control was set to three seconds for these files. I found that it was being modified within the following .htaccess file:

/home/xtreme59/public_html/wp-content/cache/autoptimize/.htaccess

I was able to change the following line:

Header append Cache-Control “public, immutable”

to

Header set Cache-Control “public, immutable”

However upon clearing cache the plugin rewrites the time and the problem persists. This one item causes a 10 point drop in the YSlow Score

well, that’s because by changing

Header append Cache-Control “public, immutable”
into
Header set Cache-Control “public, immutable”

you are overriding the 3s which are set elsewhere (because as you might have noticed the 3s are nowhere in AO’s .htaccess).

the only *real* solution is to find where the 3s are set and to remove that. As I wrote earlier, this probably is in wp-content/cache/.htaccess or wp-content/.htaccces or /.htaccess.

OK. So what should the htacess file look like for the autoptimize folder so I can return it to its original state.

There is a 3 in the wpcontent access file. I removed that one line completely and deleted cache seems to have improved and I dont see the autoptimize lines anymore. I guess I need to put back the original for the plugin?

I guess I need to put back the original for the plugin?

no, simply remove wp-content/cache/autoptimize/.htaccess and it will be re-created automatically ??