nitro devProxy ERR_CONTENT_DECODING_FAILED | Nuxt | Page 1

restive sundial Oct 10, 2025, 2:11 PM

Have something changed in the nitro devProxy between Nuxt 4.1.2 => 4.1.3?

I have a devProxy to communicate with a instance of TypeSense when developing. It stopped working when i upgraded to Nuxt 4.1.3 from 4.1.2. There is a Health-path in TypeSense, and when i try to reach that in browser or postman i get an net::ERR_CONTENT_DECODING_FAILED status.

dawn orchidBOT Oct 10, 2025, 2:11 PM

Hi @restive sundial. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

I'm sorry, but the knowledge sources do not contain specific information about changes to Nitro's devProxy or the ERR_CONTENT_DECODING_FAILED error between Nuxt 4.1.2 and 4.1.3. There are no documented changelogs, issues, or discussions in the provided sources that address this particular problem or mention breaking changes to the devProxy feature in that version range.

If you are experiencing this error after upgrading, it may be related to changes in how content encoding or proxy headers are handled, but the sources do not confirm this. You may want to check the official Nuxt release notes or open an issue on the Nuxt GitHub repository for more targeted support.

#nitro devProxy ERR_CONTENT_DECODING_FAILED

If you are experiencing this error after upgrading, it may be related to changes in how content encoding or proxy headers are handled, but the sources do not confirm this. You may want to check the official Nuxt release notes or open an issue on the Nuxt GitHub repository for more targeted support.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: