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

    (@anonymized-16850768)

    Can you please provide a screenshot of your Cache Enabler settings?

    Thread Starter rpmoscar

    (@rpmoscar)

    I went back to version 1.3.5 and it works perfect.

    This is the configuration of 1.4.1: https://ibb.co/cgjMHhx

    Anonymous User 16850768

    (@anonymized-16850768)

    Thank you for the additional information, @rpmoscar. To help identify the cause, does this still occur if you disable the pre-compression option in the Cache Behavior setting?

    Thread Starter rpmoscar

    (@rpmoscar)

    Thanks @coreyk, this prevents problem.

    Is there a way to correct this behavior by enabling the re-compression option? before it worked with version 1.3.5

    Anonymous User 16850768

    (@anonymized-16850768)

    Great! I think I know what’s occurring. This looks like an encoding issue with PHP. Is UTF-8 encoding defined?

    A new version will be released shortly to address the issue where it looks like PHP always seems to be delivering the file. Previously this was not occurring so you likely never ran into this issue.

    Anonymous User 16850768

    (@anonymized-16850768)

    Does this issue still occur with version 1.4.2?

    Thread Starter rpmoscar

    (@rpmoscar)

    I just upgraded to version 1.4.2 and the problem persists. The pre-compression option remains disabled to avoid the error.

    Is UTF-8 encoding defined?

    I think so, I try to use UTF-8 encoding. Is there a technical way to verify what you ask? Thank you.

    Anonymous User 16850768

    (@anonymized-16850768)

    To continue troubleshooting this further, are you running this on a single or network installation? Are you using the advanced configuration?

    If you’re not using the advanced configuration, when the page encounters this issue can you please check the X-Cache-Handler response header value?

    If it’s related to an encoding issue with PHP you can check if a different character set has been set in the php.ini file. The default_charset directive should be set to UTF-8, which is the default, for example:

    default_charset = "UTF-8"

    Thread Starter rpmoscar

    (@rpmoscar)

    single or network installation?

    Single

    Are you using the advanced configuration?

    Yes

    If you’re not using the advanced configuration….. X-Cache-Handler response header value?

    Enabled and disabled advanced configuration -> x-cache-handler: php

    The default_charset directive should be set to UTF-8

    Yes

    Anonymous User 16850768

    (@anonymized-16850768)

    Thanks for the additional information, @rpmoscar. Can you please update your advanced configuration snippet to include the scheme that your website uses? For example, instead of index.html.gz it would be https-index.html.gz if your website uses HTTPS (http if your website uses HTTP). This would need to be updated in multiple places in the advanced configuration snippet. (We’ll be updating the advanced configuration documentation for version 1.4+ shortly.)

    Does this resolve the issue that you’re experiencing?

Viewing 10 replies - 1 through 10 (of 10 total)

The topic ‘Coding or decompression problem? v1.4.1’ is closed to new replies.