Rank, 14 days: 8 on the Next.js sheet
2 people reported

All time, since Aug 27.

Route handlers not compressed

“Route handler responses go out uncompressed.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/next-js/issues/4336/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Route handler responses never gzipped under next start. Pages get Content-Encoding: gzip, but route handlers, including metadata routes like sitemap.xml, are sent uncompressed despite default compress: true.

Is this your bug?

File my report
Where
Route handlers
Versions
16.2.10 to 16.4.2
Platforms
Linux, Windows
How bad
Breaks a normal workflow.

Not quite your bug?

  1. Content-Encoding header dropped2 people

Original reports2, newest first

  1. Route handler responses are never gzipped with next start (Content-Type becomes an array in NodeNextResponse.appendHeader)On GitHub#101474
  2. next start built-in compression never applies to Route Handlers (including metadata routes) — sitemap.xml served uncompressedOn GitHub#98007

Do you work on Next.js?

Claim its RAP Sheet to see what your users report and answer them in one place.