• Resolved cloudshift

    (@cloudshift)


    After updating to 1.7.0 PHP is in use again on our NGINX server, which was bypassed completely before. The x-handler cache-enabler-engine is visible again, which was gone before. In general, we experience a measurable slowdown of all of our websites.

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

Viewing 4 replies - 1 through 4 (of 4 total)
  • Anonymous User 16850768

    (@anonymized-16850768)

    I apologize for the inconvenience that was caused. That was related to the advanced configuration that needed to be updated. When taking a look at your website it looks like you were able to resolve the issue based on the HTML comment being from version 1.7+ and the X-Cache-Handler response header not being set. Are you still experiencing this issue?

    Thread Starter cloudshift

    (@cloudshift)

    Thanks for the answer. The cache works but still the “x-cache-handler: cache-enabler-engine” is visible which was completely gone before. So still at least some PHP is processed, and we were not able to solve this so far.

    Anonymous User 16850768

    (@anonymized-16850768)

    When making a test request to your server I’m not seeing the X-Cache-Handler response header while the response body contains the Cache Enabler HTML comment, for example:

    curl -s -D - -o ~/Downloads/https-index.html https://www.cloudshift.de
    HTTP/2 200
    server: nginx
    date: Fri, 26 Mar 2021 16:34:38 GMT
    content-type: text/html
    content-length: 86929
    last-modified: Fri, 26 Mar 2021 15:38:47 GMT
    vary: Accept-Encoding
    etag: "605e0007-15391"
    feature-policy: geolocation 'none'; camera 'none';
    strict-transport-security: max-age=63072000; includeSubdomains; preload
    x-frame-options: SAMEORIGIN
    x-xss-protection: 1; mode=block
    x-content-type-options: nosniff
    referrer-policy: strict-origin-when-cross-origin
    accept-ranges: bytes

    The response body received then contains the following:

    ...
    </body> </html><!-- Cache Enabler by KeyCDN @ Fri, 26 Mar 2021 15:38:47 GMT (https-index.html) -->

    Furthermore, I see the same when visiting that page in a browser.

    If you’re still experiencing this you will just want to update the advanced configuration. (This may need to be adjusted to fix your exact specifications.)

    • This reply was modified 3 years, 8 months ago by Anonymous User 16850768.
    Thread Starter cloudshift

    (@cloudshift)

    You are right. We were able to fix it. Now everything seems to work like expected again. Thank yo very much for your help!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Massive slowdown after update to 1.7.0’ is closed to new replies.