Wrong nginx recommendations in docs

  • Resolved ram108

    (@ram108)


    4 years, 3 months ago

    Has anything changed in the latest plugin update? May be cache file names? Before that, everything worked fine.

    Now I see these files in cache dir:
    /cache-enabler/domain.com/https-index.html

    But documentation say:
    set $cache_enabler_uri '${custom_subdir}/wp-content/cache/cache-enabler/${http_host}${cache_uri}index.html';

    Source: https://www.keycdn.com/support/wordpress-cache-enabler-plugin

    With new filenames they will never be served with nginx.

    • This topic was modified 4 years, 3 months ago by ram108.
    • This topic was modified 4 years, 3 months ago by ram108.
Viewing 8 replies - 16 through 23 (of 23 total)

  • I have 50% more server load since the update to 1.4.x. I was already wondering. It’s not nice that this adjustment has been done without notice. :-/

    Anonymous User 16850768

    (@anonymized-16850768)

    @mobiflip you would make the following changes to that snippet:

    1. index.html to https-index.html. In your case it’s in two locations.
    2. index.html.gz to https-index.html.gz. In your case it’s in two locations.

    If you don’t use HTTPS you would use http instead. (I should be able to make this value dynamic when the documentation is updated and tested.)

    Thanks. I’ll try that! double https is correct?

    https-https-index.html.gz

    Anonymous User 16850768

    (@anonymized-16850768)

    You’re welcome. It should be https-index.html.gz if your website is using HTTPS (which is recommended).

    Thanks. I only use https. It seems to be working. The cache handler wp is no longer present and the cached page is delivered.

    Thread Starter ram108

    (@ram108)

    @coreyk @mobiflip

    https-index.html.gz

    This entry cannot be used, it will cause an error. The server will pick up the compressed files by itself if found.

    Correct: https-index.html

    Thread Starter ram108

    (@ram108)

    @coreyk

    Another interesting graph that shows how important it is to use nginx or apache to directly serve cache files, not a php interpreter.

    See graph: https://ibb.co/YDC9F0f

    Until August 18th, we have been using Cache Enabler for a very long time. You can see CPU load on the graph.

    On August 18, a new version of Cache Enabler 1.4 was released, which changed the names of cache files, as a result, nginx stopped serving files directly and began to use the php interpreter.

    The graph shows how the processor load has increased in several times. The load was noticed and analyzed.

    Nginx settings have been updated to directly handle cache files with new names. As a result, the server load returned to its previous, almost zero values.

    Anonymous User 16850768

    (@anonymized-16850768)

    That’s a great representation. Thank you for sharing, @ram108.

Viewing 8 replies - 16 through 23 (of 23 total)
  • The topic ‘Wrong nginx recommendations in docs’ is closed to new replies.