Applicable to:
- Plesk for Linux
Symptoms
-
Cache expiration is enabled in nginx according to the article with expiration time set explicitly, but cache expiration headers are not returned:
# wget -S https://example.com/wp-content/uploads/file.jpg 2>&1 | egrep "Server|Content-Type|Cache-Control|Expires"
Server: nginx
Content-Type: image/jpeg -
Wordpress is installed.
-
In Domains > example.com > PHP Settings for a domain PHP handler is set as FPM application served by nginx.
Cause
This is Plesk internal issue with ID #PPPM-4413, which is planned to be fixed in future Plesk updates
Resolution
As a temporal workaround, apply the following solution:
-
Change PHP handler to FPM application served by Apache in Domains > example.com > PHP Settings.
-
Check if Leveraging Browser Caching for nginx is enabled, for example:
# wget -S https://example.com/wp-content/uploads/file.jpg 2>&1 | egrep "Server|Content-Type|Cache-Control|Expires"
Server: nginx
Content-Type: image/jpeg
Expires: Thu, 05 Oct 2017 20:36:13 GMT
Cache-Control: max-age=604800# curl -I -c - "https://example.com/wp-content/uploads/file.jpg" -k
...
Expires: Thu, 05 Oct 2017 20:53:53 GMT
Cache-Control: max-age=604800
...
Additional information
Additional nginx directives/Leverage browser caching are ignored for WordPress website
Comments
12 comments
What is the exact change because the current configuration is for a domain PHP handler is set as "FPM application served by Apache". And also the workaround states the same thing:
Change PHP handler to "FPM application served by Apache" in Domains > example.com > Hosting settings .
Hi @gli Pançi, do you mean that handler is set to "FPM application served by Apache" and cache expiration is enabled in nginx but cache expiration headers are not returned by server?
I have FPM application served by Apache and nginx in proxy mode.
Despite the change I never see the cache-control header.
Hi @David,
If expire headers are not working with Apache, another reason might be involved. Please submit request to a support in order to investigate it thoroughly: https://support.plesk.com/hc/en-us/articles/213608509-How-to-submit-a-request-to-Plesk-support-
Hi,
I found the fix that worked:
https://support.plesk.com/hc/en-us/articles/360014674853-Additional-nginx-directives-Leverage-browser-caching-are-ignored-for-a-WordPress-website
Thank you
Hi @Matthias,
Thank you for the provided way!
I added a link to this article in the "Additional information" section in order to help others, who have the applied Hotlink protection security measure in WordPress as you, to resolve the issue
Looks like it works fine once "Hotlink protection" is disabled. Spent about 1 hour trying to fix it on a new domain - didn't suspect Plesk initated update. Just in case, I got 3.6.1-1603 of WP Toolkit and Version 17.8.11 Update #40 of Plesk.
Hi @Mikhail Krivoshein,
You hit another bug here that is documented on the following link: https://support.plesk.com/hc/en-us/articles/360014674853-Additional-nginx-directives-Leverage-browser-caching-are-ignored-for-WordPress-website
its still not entirely fixed though, but will be fixed soon!
Hey guys,
Not sure if the fix has been released yet,
I've got fresh version of Plesk, fully updated, and expiry headers are not being applied, not only in WordPress, but in any site, including static HTML.
If you could give me an update.
Thanks
Hello @Rafal,
Indeed, it is not fixed yet. It is planned to be fixed in the next major Plesk release.
For now, please, use the workaround specified in this article.
I'm afraid this isn't possible, entire Hosting environment is configured for NGINX.
Any ETA on the next Plesk release?
@Rafal,
Right now there is no precise ETA for the release.
After the fix will be ready this article will be updated with the corresponding information.
Additionally, the description of releases and fixed issues may be found here: https://docs.plesk.com/release-notes/onyx/change-log/
Please sign in to leave a comment.