ERR_CONTENT_DECODING_FAILED

  • bash88

    (@bash88)


    8 years, 8 months ago

    Hi Guys,

    I’ve been using this plugin for quite some time now. Everything has always worked smoothly, until a couple of weeks ago (maybe this has something to do with the WP 4.8 update).

    When the plugin is activated, Chrome shows an ERR_CONTENT_DECODING_FAILED error really short and then reloads the page automatically, displaying the page properly. Firefox insists on showing the ERR_CONTENT_DECODING_FAILED page until the user decides to reload the page.

    I don’t think I changed anything in the plugin settings. I did update to WP 4.8 some time ago, so maybe this has something to do with it.

    Could you help me solve this?

Viewing 15 replies - 1 through 15 (of 18 total)
1 2
  • Ben

    (@benbornschein)

    8 years, 8 months ago

    Hi,

    did you tried to clear WP Super Cache’s cache and your browser’s cache?
    Did you use any other caching plugin before using WP Super Cache?

    Thread Starter bash88

    (@bash88)

    8 years, 8 months ago

    Hi Ben,

    Thanks for your quick response. I deleted the whole cache folder on the server and I’m checking out the website in incognito mode. So there’s no cache left behind, I think.

    No other caching plugins are involved here.

    Ben

    (@benbornschein)

    8 years, 8 months ago

    Can you try to disable the “compress pages” option and check it again?

    Thread Starter bash88

    (@bash88)

    8 years, 8 months ago

    That does fix the problem.

    Would you also happen to know what the problem is here?

    Ben

    (@benbornschein)

    8 years, 8 months ago

    Can be two things:

    1. Memory of the server has an error (if the issue is not persistent for the same page, it is the memory)
    2. Something corrupts the page before or while WP Super Cache tries to compress the page.

    Thread Starter bash88

    (@bash88)

    8 years, 8 months ago

    The issue was completely persistent for all pages. First time page load after clearing the cache = error. After that, fine. So based on your info I don’t think it’s the memory.

    I see now that the files compressed by my minifying plugin generate the same error. Completely unrelated to WP super cache, but then maybe the WP 4.8 update changed something in compression which affects both plugins?

    Is the compression done through a WP function or something?

    Ben

    (@benbornschein)

    8 years, 8 months ago

    Did your minifying plugin worked before while WP Super Cache was active and compressed the pages?

    Thread Starter bash88

    (@bash88)

    8 years, 8 months ago

    Yes, the minifying plugin has always worked as expected.

    I disabled both WP super cache and the minifying plugin when I noticed the issue last week.

    WP super cache is now active without compression. When I activate the minifying plugin the minified files generate the same ERR_CONTENT_DECODING_FAILED error in the console the page compression in WP Super cache did.

    Ben

    (@benbornschein)

    8 years, 8 months ago

    You can try to disable every other plugin and select the WordPress default theme. Then try again to activate “compress pages” and check, if the error is gone.

    Thread Starter bash88

    (@bash88)

    8 years, 8 months ago

    Do you know if the compression is done through a WP function?

    Ben

    (@benbornschein)

    8 years, 8 months ago

    No, it’s just the php function ob_gzhandler/zlib.output-compression that is used by most plugins to compress the data.

    Thread Starter bash88

    (@bash88)

    8 years, 8 months ago

    Ben,

    Thank you very much for taking the time to help.

    In the end it turns out it’s another plugin unrelated to both WP Super Cache and the minifying plugin causing the issue.

    Ben

    (@benbornschein)

    8 years, 8 months ago

    Great, which plugin has caused the error?

    • This reply was modified 8 years, 8 months ago by Ben.
    Thread Starter bash88

    (@bash88)

    8 years, 8 months ago

    A custom plugin by a supplier. Not really worth mentioning the name here.

    I guess it’s going to turn out to be something like this (found this in another thread):

    “It was caused by an extra space after the closing ?> in a plugin file…”

    Ben

    (@benbornschein)

    8 years, 8 months ago

    Yes, if any whitespace/char is outputted before ob_start(); is started or after ob_end_clean(); stopped, the complete process fails.

Viewing 15 replies - 1 through 15 (of 18 total)
1 2

The topic ‘ERR_CONTENT_DECODING_FAILED’ is closed to new replies.