Raam Dev

@xberg We're hoping to have a release out within the next week or two. This GitHub issue will be updated once a release occurs.

> the page is actually "changing" content for every request, even though 99.999% of its source is unchanged? Quick Cache isn't actually changing the content of the page (or more...

@jaswsinc writes... > Comet Cache removes `Last-Modified` headers because WordPress itself removes `Last-Modified` to avoid compatibility issues when the desire is to prevent browser caching. See: https://developer.wordpress.org/reference/functions/nocache_headers/ > Discussion: https://core.trac.wordpress.org/ticket/22258...

Related: https://github.com/websharks/zencache/issues/371 https://github.com/websharks/zencache/issues/134

This issue was opened several years ago as a feature request for `ETags` and `If-Modified-Since`. This issue now contains lots of outdated information (e.g., `ETags` is now supported by Comet...

> Or maybe offer a button "Reinstall the current version". I like the idea of changing the text of that button to "Reinstall Current Version" when the latest version is...

It looks like we actually _don't_ want to use Closures in `plugin.php`, since the code in that file where we use `create_function()` is code designed to show error notices for...

+1. Cool idea.

## Interim Solution This can be achieved by using the WP Crontrol plugin + the Comet Cache API to schedule custom Clear Cache events of any type; see this updated...

Posting a list of downsides to the `mod_rewrite` approach that we discussed internally: Using `mod_rewrite` will: - Not work on Nginx servers. - Become somewhat dependent on the Apache modules...