Disabled HTTP compression but some responses are still being compressed

[tuhlaajapoika]

Hello,

My Jellyseerr instance is running behind an NGINX reverse proxy that handles HTTP data compression. I've patched and built Jellyseerr to prevent it from compressing before passing them to the reverse proxy. I modified next.config.js as described on the Next.js documentation, which worked fine before v2.x.

However, after v2.x, some responses are still being precompressed and I can't figure out which part of the code (or its dependencies) is applying the compression. Data that is being compressed is provided by Express.

I'm unsure how to identify the changes made on v2.x onwards to adjust my patches accordingly. I'm relatively new to Node.js applications and the list of dependencies is a bit overwhelming to be honest. Should I make changes to server/index.ts to explicitly disable compression?

Patch for next.config.js

diff --unified --recursive --text --color a/next.config.js b/next.config.js
--- a/next.config.js	2024-06-13 14:28:59.908618620 +0300
+++ b/next.config.js	2024-06-13 14:29:52.302294307 +0300
@@ -21,6 +21,7 @@
 
     return config;
   },
+  compress: false,
   experimental: {
     scrollRestoration: true,
     largePageDataBytes: 256000,

[gauthier-th]

Did you delete the dist, .next, and node_modules directories before rebuilding Jellyseerr?
What responses are still compressed?

[tuhlaajapoika]

Sorry for the late response.

It was a fresh build on a cloud server. After testing throughly with curl it seems that Jellyseerr works as it should. It was a misunderstanding from my part. Firefox's developer tools keeps showing "Content-Encoding: gzip" on random .css and .js files so it might be a response from a CDN or a another server. Curl does not receive Content-Encoding header for the same URL.

Thank you for the reply, though.