On Jun 18, 2013, at 13:59, Forrest L Norvell <[email protected]> wrote:
> So express-domain-middleware will wrap up each request into a domain, but > then you'll also need to add the default Express error handler at the end of > your middleware chain to actually handle the error and return something other > than a 200 status. Right, the code I posted in my gist does that. I have a default express error handler at the end of my middleware chain, and it works fine for reporting 404 errors or errors in downloading the url. My problem at the moment is that when an error occurs in the process I spawned, that error does not get sent to that express error handler. I have attached a listener for the error event to the process. This listener is working correctly, because I can log the error to the console. Then I call next(err) but my express error handler is never invoked. What do I need to do to handle these errors and report them to the browser? -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
