• Resolved lesdeuxpiedsdehors

    (@lesdeuxpiedsdehors)


    Hello,

    I know that this subject has already been discussed by others, but I have a problem with the use of Autoptimize and Cloudflare. I use the page rule “Cache everything” on Cloudfare and I often encounter the 404 issue on Autoptimize js files.

    If I understood correctly, by using the “Cache Everything” page rule on Cloudfare, the HTML of my page is cached on Cloudfare incorporating the JS/CSS optimization that Autoptimize has done. The problem is that in time, Autoptimze regenerates new files and when the Html page calls its files, they are no longer there, hence the 404 error.

    Is this normal as a situation? Is there a solution? Because the problem is that every time I encounter this problem, I have display problems.

    Is there a way to purge the Cloudflare cache automatically as soon as Autoptimize regenerates CSS/js files?

    Thank you,
    Sylvain

    The page I need help with: [log in to see the link]

Viewing 3 replies - 31 through 33 (of 33 total)
  • Thread Starter lesdeuxpiedsdehors

    (@lesdeuxpiedsdehors)

    Hi Franck,

    Quick follow up here. I installed the WP CF Super cacher plugin. I’m experiencing some trouble with it but I’m talking with the dev to work this out.

    In the meantime, I wanted to ask you something. What does “expired” mean on Autoptimize file (wp-content/cache/autoptimize/css/autoptimize_e45fee050badda6bf1cc0986c0a8c840.css) here.

    It changed in a few hours (or less) as you can see here.

    Is this a problem or not at all and it’s normal? I just want to understand ??

    Plugin Author Optimizing Matters

    (@optimizingmatters)

    that’s cloudflare saying the resource in their cache expired and was re-fetched; it’s normal.

    Thread Starter lesdeuxpiedsdehors

    (@lesdeuxpiedsdehors)

    Ok thanks for the confirmation then !

Viewing 3 replies - 31 through 33 (of 33 total)
  • The topic ‘404 with Autoptimze and Cloudfare’ is closed to new replies.