Submit Feedback
Legacy Knowledge Base
Published Sep. 10, 2025

ERR_CONTENT_DECODING_FAILED

Written By

Apsara Raheja

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • When the user is accessing their DMS application, sometimes they encounter the below error in the browser console:
    Error :

    Failed to load resource: net::ERR_CONTENT_DECODING_FAILED.

    http://localhost:8080/download-resource-portlet/js/main.js?browserId=other&minifierType=js&languageId=en_US&b=6210&t=1507734873000 net::ERR_CONTENT_DECODING_FAILED 200 (OK)

Environment

  • Liferay DXP 7.0

Resolution

  • This error mostly comes when there are mismatches in compression between the server and the browser. Hence, the user needs to verify that the server is correctly configured for GZIP compression and that the `Content-Encoding: gzip` header is being sent with the `main.js` file.
  • To resolve the error, check if any below properties were added in portal-ext.properties:
    1. com.liferay.portal.servlet.filters.gzip.GZipFilter=true
    2. minifier.enabled=false
    3. gzip.compression.enabled=false
  • If yes, remove these properties and restart the clean server.

Additional Information

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?