Skip to content

Errors / Network errors

net::ERR_CONTENT_LENGTH_MISMATCH

The server said a file would be a certain size and then sent less.

A truncated file: a script that fails, an image half drawn.

Why it happens

  • The server or proxy stopped sending partway: a timeout, a full disk, a worker killed mid-response.
  • A Content-Length computed before compression or a rewrite changed the body.
  • ERR_INCOMPLETE_CHUNKED_ENCODING is the same when the size was not announced.

How to fix it

  1. Check the proxy's buffers and temporary disk space (nginx's proxy temp directory filling up is common).
  2. Do not set Content-Length by hand on a body something else compresses.
  3. It tends to appear on large files first (a video, a big JavaScript bundle, a PDF), because they take longest to send and so meet a timeout or a full disk first. Reload with DevTools' Network panel open and compare the size received with the announced Content-Length on that request; a file cut short at the same point every time points at a buffer or a limit.

Whose problem it is

Usually the server that answers the request.

Does your site have it?

Free, no account. We open your page and four more in a clean Chrome and list every error like this one, with the page and the click that caused it. How the free page check works.

Check only sites you run or have permission to check.