Content Encoding Error

[dylang]

In Chrome I get a blank error page, in Firefox I get this:

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.

curl -v -H "Accept-Encoding: gzip, deflate" --compressed http://localhost:9000/ works correctly.

I'm using compression via connect 2.19.6 via grunt-contrib-connect and I'm not sure how to best debug the issue. Our code was working at least until last week, but stopped working about today (maybe around July 17) , so I'm wondering if a new dependency broke something.

Unfortinly our code isn't open source so I can't share it, but we're including compression via the connect.compress() middleware which precedes the other middleware.

[dougwilson]

I'm really sorry, but nothing has changed recently. There was a new version of this module yesterday, but the version in connect is not affected by this and it's only change is to add debugging.

I verified that this module is compressing and working in Firefox. Unless you provide some code test case that demonstrates the issue we can use to reproduce or you identify the issue and tell us what to fix, there is nothing we can act on.

[dougwilson]

Also to be clear I'm' not definitively saying there is no issue with this module, but I have no idea what it would be. You do not have to post your IP code, but if you can make a simple example that demonstrates the issue would be necessary for us to investigate.

[dylang]

👍 I agree with what you wrote. Thanks for taking the time to reply.

I created this issue to see if there was a good resource I could use to debug the cause of the problem because I agree it's probably not caused by compression or connect and it's probably caused by the part of our code that I can't share. It's been a few years since I've built middleware for connect and was hoping there was something I wasn't aware of to assist with debugging.

For now my team is going to disable compression until we have more time to look into it. This is just for development and SauceLabs testing, not production, so it's not a big deal. Thanks again!

[dougwilson]

No problem. As for what is the cause, I really don't know where to start, because the only real thing that would go wrong here is if you are replacing res.end or res.write in your code and simply implementing it with false assumptions (like replacing the reference at some point with the core implementation instead of the previous implementation).