ERR_HTTP_HEADERS_SENT: Cannot set headers after they are sent to the client

by

That particular error occurs whenever you try to send more than one response to the same request and is usually caused by improper asynchronous code.

The code you show in your question does not appear like it would cause that error, but I do see code in a different route here that would cause that error.

Where you have this:

if (!user) {
  errors.email = "User not found";
  res.status(404).json({ errors });
}

You need to change it to:

if (!user) {
  errors.email = "User not found";
  res.status(404).json({ errors });
  // stop further execution in this callback
  return;
}

You don’t want the code to continue after you’ve done res.status(404).json({ errors }); because it will then try to send another response.

In addition, everywhere you have this:

if (err) throw err;

inside an async callback, you need to replace that with something that actually sends an error response such as:

if (err) {
    console.log(err);
    res.sendStatus(500);
    return;
}

throwing inside an async callback just goes back into the node.js event system and isn’t thrown to anywhere that you can actually catch it. Further, it doesn’t send a response to the http request. In otherwords, it doesn’t really do what the server is supposed to do. So, do yourself a favor and never write that code in your server. When you get an error, send an error response.

Since it looks like you may be new here, I wanted to compliment you on including a link to your full source code at https://github.com/lourdesr/devlog because it’s only by looking at that that I was able to see this place where the error is occuring.

More Related Contents:

  1. passport.js passport.initialize() middleware not in use
  2. Push items into mongo array via mongoose
  3. Understanding passport serialize deserialize
  4. Avoid “current URL string parser is deprecated” warning by setting useNewUrlParser to true
  5. Cannot overwrite model once compiled Mongoose
  6. MongoDB/Mongoose querying at a specific date?
  7. How to implement a secure REST API with node.js
  8. add created_at and updated_at fields to mongoose schemas
  9. How to populate a sub-document in mongoose after creating it?
  10. passport’s req.isAuthenticated always returning false, even when I hardcode done(null, true)
  11. mongoose custom validation using 2 fields
  12. How to protect the password field in Mongoose/MongoDB so it won’t return in a query when I populate collections?
  13. Mongoose .find() method causes requests to hang
  14. Redirecting to previous page after authentication in node.js using passport.js
  15. Using PassportJS, how does one pass additional form fields to the local authentication strategy?
  16. Mongoose update without callback
  17. Node + Express + Passport: req.user Undefined
  18. Uploading images using Node.js, Express, and Mongoose
  19. Model.find().toArray() claiming to not have .toArray() method
  20. How to fix ‘Error: querySrv EREFUSED’ when connecting to MongoDB Atlas?
  21. How to know if user is logged in with passport.js?
  22. Model.find() returns empty in mongoose [duplicate]
  23. Mongoose – caused by :: 11000 E11000 duplicate key error index?
  24. Mongoose Schema Error: “Cast to string failed for value” when pushing object to empty array
  25. What does body-parser do with express?
  26. Why does mongoose always add an s to the end of my collection name
  27. How do I setup a SSL certificate for an express.js server?
  28. Mongoose (mongodb) batch insert?
  29. Which SchemaType in Mongoose is Best for Timestamp?
  30. Mongoose multiple connections

Leave a Comment