Viewing 4 replies - 1 through 4 (of 4 total)
  • given that even your autoptimize-files have very limited cache-ability (normally ao-files have a 1y validity), either:
    * you’re not on apache
    * you have an apache that is configured in such a manner that .htaccess-based expiry-settings aren’t honored
    * cloudflare (which you are using) isn’t “forwarding” the original expires-/ cache-control headers

    hope this clarifies,
    frank (ao dev)

    Thread Starter saajanbedi

    (@saajanbedi)

    Thanks for reply ,Expires Module for Apache Was not Installed & Browser Cache Expiration was set for 4 hours in Cloudflare. what is the recommended expiration (I have set it to 1 month)

    a month should be good, yes ??

    Hi Someone,

    Maybe it’s not correct to put my issue here but I can not post new issue. Juts put here.

    i accidentally fill in huge big number into Cache Timeout and Scheduler Timer.
    My issue is “Next scheduled garbage collection will be at 1948-10-05 17:47:35 UTC” whatever I changed Cache Timeout and Scheduler Timer can not change “1948-10-05 17:47:35 UTC”. I also go to database wp_options and can not find how to change “Next scheduled garbage collection will be at 1948-10-05 17:47:35 UTC”.

    My issue is Preload and Garbage Collection are always looping and never stopped.

    Whatever I uninstall WP Super Cache and reinstall new one and can not fix this issue.

    Somebody know how to fix this issue?

    my email is [email protected]
    Thanks

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Leverage browser caching Problem’ is closed to new replies.