Error: Firefox - Content Encoding Error / Google Chrome - Error 330 (net::ERR_CONTENT_DECODING_FAILED): Unknown error.

When you open a PHP page in your Firefox, you get the following error:

Content Encoding Error 

The page you are trying to view cannot be shown because it uses an invalid or unsupported form of compression.

* Please contact the website owners to inform them of this problem.

In Google Chrome, you get the following error:

Error 330 (net::ERR_CONTENT_DECODING_FAILED): Unknown error.



The solution is to turn on 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

On Fedora/CentOS/RedHat, it's /etc/php.ini:

vi /etc/php.ini

Find the zlib.output_compression line and turn zlib.output_compression on:

zlib.output_compression = On

Restart Apache afterwards:

On Debian/Ubuntu, you run:

/etc/init.d/apache2 restart

On Fedora/CentOS/RedHat, you run:

/etc/init.d/httpd restart
Share this page:

Suggested articles

7 Comment(s)

Add comment


By: ShaunaTexis

Chrome error is not something unique happened to you.
Sometimes there is a dreadful total crash of the browser and sometime it sends ddifferent errors, upon restarting nothing happens.
Such sorts of errors can be linked to the file association issues. The file association references are the important components of the registry database in Windows. A registry repair scan, which has the power to fix file association errors, will help you to find the solution for Google chrome error.

I fixed this error after reading this article  chrome error, google chrome error

Hope you might get help from this article too.

By: Patrick

this is great if your the developer, what do we do if I am on linux and run into this problem quite frequently?

By: Kd

i was the problem of Error 330 (net::ERR_CONTENT_DECODING_FAILED) then i just turn on zlib.output_compression but it still on working now pages shows different erro 

 The requested URL /forum/forum/25/yahoo/ was not found on this server.

Apache/2.2.3 (Red Hat) Server at Port 80

By: Mark Poulding

Can confirm this worked perfectly for me, running a cms on plesk.

By: Loganathan

When i stuck with this problem, i can't able to find the exact solution, but this page is reall helpful

By: KUPERnick

This was very helpful. Thank You!!

By: Computer Dynamics / VIP Hawaii

Yes, this worked for me! Thanks!!! :)