How To Fix: ERR_CONTENT_DECODING_FAILED

Updated November 2024: Stop getting error messages and slow down your system with our optimization tool. Get it now at this link

1. Download and install the repair tool here.
2. Let it scan your computer.
3. The tool will then repair your computer.

ERR_CONTENT_DECODING_FAILED error may appear in your browser when a resource is configured on your reverse proxy and backend communication is working. In other words, the backend returns data, but not in the form expected by the browser. For example: the browser expects a response from the GZIP, but receives plain text. As a result, the decoding of the index content failed. Content received, but the browser is not able to decode / understand the data.

To fix this error, reset the Accept-Code header of the encoding request in your Reverse Proxy configuration.

Here are some possible solutions to correct the error ERR_CONTENT_DECODING_FAILED:

If you are a web developer and you receive this error in your php pages, the solution is to enable or disable zlib.output_compression in php.ini. If your web content is actually encoded, enable or disable it. Simply open your php.ini and find the line zlib.output_compression and enable or disable and save the php.ini file.

zlib.output_compression = On/Off

1. Try to save your codes in UTF8 format without BOM (Byte Order Mark). Sometimes codes written with Notepad++++ or other coding tools use UTF8 encoding and this also causes this error.
2. If you receive this error specifically on the Chrome browser, you can try to update Chrome to the latest version or reinstall it. If you use Chrome extensions, try to disable them all and access your web page. If your web page is working correctly, activate them one by one. This way, you can determine the culprit extension and disable it.
3. If you have enabled Privoxy proxy in chrome, check the suggested correction here.
4. If you have installed antivirus software on your local computer, try to turn it off for a while and reload the page that is causing you problems. This way, you can identify if the antivirus is the cause of the problem.

Enable zlib.output_compression in your php.ini

Open your php.ini. On Debian/Ubuntu, it’s /etc/php5/apache2/php.ini :

vi /etc/php5/apache2/php.ini

Under Fedora/CentOS/RedHat, it is /etc/php.ini :

vi /etc/php.ini

Find the line zlib.output_compression and activate zlib.output_compression :

zlib.output_compression = On

Restart Apache then:

On Debian/Ubuntu, you run:

/etc/init.d/apache2 restarts

Under Fedora/CentOS/RedHat, you run:

/etc/init.d/httpd restart

Disabling G-Zip encoding

Sometimes, G-Zip encoding is the reason why this error is triggered. Few browsers provide the necessary customization to disable this feature without using third-party extensions. Therefore, in this step, we will download and install an extension, then disable G-Zip encoding using this extension.

Deleting browser history and cookies

Sometimes, the browser history or cookies may be corrupted. As a result, the encoding process can be affected. Therefore, in this step, we will delete the browser history and cookies. Depending on your browser, the process may differ a little.

https://github.com/docker-library/tomcat/issues/82

Expert Tip: This repair tool scans the repositories and replaces corrupt or missing files if none of these methods have worked. It works well in most cases where the problem is due to system corruption. This tool will also optimize your system to maximize performance. It can be downloaded by Clicking Here