Improvements

  • Resolved tkwpweb

    (@tkwpweb)


    4 years, 4 months ago

    Hello,
    first of all… nice Job with this plugin. Since years i used Cache Enabler Plugin but since rewrite it has some problems. Your Plugin is a very good alternative.

    But i found one big improvement:

    When i select “Enable GZip compression” you save only the compressed file under – /wp-content/cache/powered-cache/ – folder but not the uncompressed html file.

    I used an customized nginx config.

    In my case your plugin save “index-https.html_gzip”. Why?

    Why you cant save like this:
    index-https.html (normal uncompressed file)
    index-https.html.gz (compressed file if checked in settings)

    This would be much better on server side. E.g. Better compatibility and “gzip_static” works out of-the-Box.

    Compatibility?
    “_gzip” needs custom settings in nginx config to work (otherwise PHP do this redirect = bad performance). But when use “.gz” its compatible with most basic nginx configs because this is default “gzip_static on;” setting. Works fine and performant without PHP.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Mustafa Uysal

    (@m_uysl)

    Hi @tkwpweb,

    Sorry for the delay here.

    Why you cant save like this:
    index-https.html (normal uncompressed file)
    index-https.html.gz (compressed file if checked in settings)

    Thanks for the suggestion, saving the cache output as html.gz might be a better choice in terms of naming but I didn’t like the approach for saving both compressed & uncompressed data.

    Also, why would you need to turn on the gzip feature when you can control the gzip with your Nginx settings? That feature useful when you can’t control the gzip feature on the webserver.

    Thread Starter tkwpweb

    (@tkwpweb)

    Its very easy to say to have both versions:

    There is the most powerful solution.

    NGINX can serve the .gz version directly with gzip_static function. This is much much much better then every time compress “on-the-fly”.

    If there are both versions NGINX can serve the .html direct with try_files and the .gz with gzip_static -> this is the most powerful solution.

    I dont know why you restrict the performance from your plugin.

    Plugin Author Mustafa Uysal

    (@m_uysl)

    @@tkwpweb The gzipped filename has been changed in version 2.0, it uses .gz extension that you can leverage on gzip_static.

    Thanks for the feedback, marking as resolved now.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Improvements’ is closed to new replies.