Error: Cannot Set Headers After They Are Sent to the Client

Nilesh Raut Posted on May 31           Error: Cannot Set Headers After They Are Sent to the Client # node # tutorial # programming # javascript Debugging (2 Part Series) 1 Why Debugging Skills Matter More Than Writing New Code 2 Error: Cannot Set Headers After They Are Sent to the Client Error: Cannot Set Headers After They Are Sent to the Client If you've built APIs with Express for any length of time, you've probably seen this error: Error [ ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client Enter fullscreen mode Exit fullscreen mode Or: Cannot set headers after they are sent to the client Enter fullscreen mode Exit fullscreen mode The frustrating part is that the application often works for some requests and fails only under specific conditions. This error is almost always caused by sending multiple responses for the same request. Let's break down why it happens and how to prevent it in production code. Problem Consider this Express route: app . get ( " /users/:id " , ( req , res ) => { if ( ! req . params . id ) { res . status ( 400 ). json ({ error : " User ID required " }); } res . json ({ id : req . params . id }); }); Enter fullscreen mode Exit fullscreen mode Looks harmless. But if the first response is sent, Express continues executing the remaining code. Result: Error [ ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client Enter fullscreen mode Exit fullscreen mode The server attempts to send two responses for a single request. HTTP doesn't allow that. Why It Happens A request can only receive one response. Once Express sends: res . send (); Enter fullscreen mode Exit fullscreen mode or res . json (); Enter fullscreen mode Exit fullscreen mode or res . redirect (); Enter fullscreen mode Exit fullscreen mode or res . end (); Enter fullscreen mode Exit fullscreen mode the HTTP headers are already transmitted. Any attempt to modify headers or send another response will trigger the e