Disabling Transfer-Encoding: chunked on production. #38606

deepsyx · 2022-07-13T15:20:35Z

deepsyx
Jul 13, 2022

Hello,
We've been using NextJS 12.1.0 with Cloudfront successfully for some time. So far the next compress was set to false and we relied on AWS Cloudfront to compress the files (brotli/gzip).

Recently we migrated to 12.2.0 and the HTTP headers from the next were changed to follow the HTTP/1.1 standard instead of the HTTP/1.0 - before the migration we received the Content-Length header (which is required for Cloudfront to work).

The file must be of a type that CloudFront compresses.

The file size must be between 1,000 and 10,000,000 bytes.
The response must include a Content-Length header so CloudFront can determine whether the file size is in the range that CloudFront compresses. If the Content-Length header is missing, CloudFront won't compress the file.
The response must not include a Content-Encoding header.

However, after we migrated to 12.2.0 all requests followed the HTTP/1.1 protocol meaning that we no longer receive Content-Length header, but we started receiving Transfer-Encoding: chunked and the files were sent in chunks.

Is there a way to bring back the old behavior without using additional reverse proxies or if not - what would be the proper solution to our problem? We'd like to not compress the files at NextJS level and only compress them at our reverse proxy.