Home > Article > Backend Development > Why does my OpenX ad server display \'Error 330 (net::ERR_CONTENT_DECODING_FAILED):\' after migrating to a new server?
Troubleshooting "Error 330 (net::ERR_CONTENT_DECODING_FAILED):"
After migrating to a new server, users encountered an issue with their OpenX ad server, displaying the "Error 330 (net::ERR_CONTENT_DECODING_FAILED):" message in Google Chrome and "The page you are trying to view cannot be shown because it uses an invalid or unsupported form of compression." in Firefox.
To address this, it's important to ensure that the PHP configuration for OpenX server is correct. OpenX requires the following settings to be enabled:
Additionally, the following PHP extensions are mandatory for OpenX:
Once these settings are verified, it's crucial to ensure that the HTTP request's headers correctly state that the content is gzip encoded. If this is not the case, turn off gzip encoding in the server settings or ensure that the content is actually encoded.
By addressing these aspects, users can resolve the "Error 330 (net::ERR_CONTENT_DECODING_FAILED):" issue and restore the proper functionality of the OpenX ad server.
The above is the detailed content of Why does my OpenX ad server display \'Error 330 (net::ERR_CONTENT_DECODING_FAILED):\' after migrating to a new server?. For more information, please follow other related articles on the PHP Chinese website!