Luc Poupard

Thank your for your feedback!

So to be clear I still need to add f_mp4 transformation on the file directly. Not that ideal but I keep it as an option and give it a try. ??

Hi both,

We face the same issue and while investigating about it, I found out that some of the images have like 1 pixel difference after regeneration!

• Before: […]-1024×803.png
• Before: […]-1024×804.png

If option to delete obsolete images is activated, the previous one is obviously removed and ends up by a 404 if used in a post.
I just saw it few minutes ago so I need to look into it further, but I’m pretty confident that this is the same.

Question is why it would regenerate the same image but with a different size?

Thank you for the explanation!
I’m gonna remove this directive and let you know if it solves my issue.

Here are the htaccess rules that are defined.
Since last week I’ve tried to define Expire header to 0 seconds for html file but it doesn’t seem to change anything.

# BEGIN Expire headers
<IfModule mod_expires.c>
ExpiresActive On
ExpiresDefault "access plus 1 month"
ExpiresByType image/x-icon "access plus 1 year"
ExpiresByType image/gif "access plus 1 year"
ExpiresByType image/png "access plus 1 year"
ExpiresByType image/jpg "access plus 1 year"
ExpiresByType image/jpeg "access plus 1 year"
ExpiresByType video/ogg "access plus 1 year"
ExpiresByType audio/ogg "access plus 1 year"
ExpiresByType video/mp4 "access plus 1 year"
ExpiresByType video/webm "access plus 1 year"
ExpiresByType application/x-font-ttf "access plus 1 year"
ExpiresByType font/opentype "access plus 1 year"
ExpiresByType application/x-font-woff "access plus 1 year"
ExpiresByType image/svg+xml "access plus 1 year"
ExpiresByType application/vnd.ms-fontobject "access plus 1 year"
ExpiresByType text/css "access plus 1 month"
ExpiresByType application/javascript "access plus 1 month"
ExpiresByType application/rss+xml "access plus 1 day"
ExpiresByType application/atom+xml "access plus 1 day"
ExpiresByType text/html "access plus 0 seconds"
</IfModule>
# END Expire headers
# BEGIN Cache-Control
<IfModule mod_headers.c>
<FilesMatch "\.(pl|php|cgi|spl|scgi|fcgi|html|htm)$">
Header unset Cache-Control
</FilesMatch>
<filesMatch ".(jpg|jpeg|png|gif|ico)$">
Header set Cache-Control "max-age=31536000, public"
</filesMatch>
<filesMatch ".(ogg|mp4|webm)$">
Header set Cache-Control "max-age=31536000, public"
</filesMatch>
<filesMatch ".(css|js)$">
Header set Cache-Control "max-age=2628000, public"
</filesMatch>
</IfModule>
# END Cache-Control

If it helps, these are headers on my page when I get cached page (as I’m logged in):
https://cloud.cdi.ch/index.php/s/MdSEefn366Cdgpx

And after a refresh (Ctrl + F5):
https://cloud.cdi.ch/index.php/s/HLJRf7oybCr5WkF

Hi!

I’m sorry for my laaaaaaate answer. As the issue is non-blocking but a bit annoying, I’ve left it on the side for a while.

I have some htaccess rules defining Expire headers and Cache Control on HTML ressources (for 2h).
Is that possible that the page is cached as user is not logged and that even after being logged, the browser still load the page in its cache (despite user being logged)?

Sorry for late answers (pretty long week-end).

Yes it happends intermittently. Different users have different behaviors: a cached page may be served to a user but not to an other user.
Cached file stop being delivered after a certain period yes. But it seems random too. Refresh the page is enough sometimes, other times event a hard refresh (Ctrl+F5) is not enough.
Clear the cache seems to be ok.

About the build of the cache, how could I know if it does while I’m logged in? Looking at the time in the Cache Enabler comment?

Indeed. That’s how I identified this issue was related to Cache Enabler.

At first I thought it was a ressources loading issue as the admin bar is at the end of the page in the code. But as I digged into it, I realized that it was serving the cached version of the page, despite the fact I’m logged in.