3 ms·

502 Bad Gateway. Too much selfdestruct?

• pilif 17y ago
  An invalid HTTP request it seems: Error: Parse Error at Stream.ondata (http:533:30) at IOWatcher.callback (net:357:31) at node.js:749:9 how the hell would I catch that one - somewhere deep inside node's HTTP library? It's restarted now. edit: I've added an uncaughtException listener so it should at least keep going. Exception handling in asynchronous code is really hard. Above exception never even reaches my own code.
  • amix 17y ago
    This error happend to me when I upgraded to 0.1.91. I didn't look into it, but I suspect the error is caused by/in node-memcache [http://github.com/elbart/node-memcache http://github.com/elbart/node-memcache]
    • pilif 17y ago
      I'm not running node-memcache, but node-redis-client and this is an issue in the parser that parses incoming requests - probably malformed ones of people trying stuff out. Incidentally, the first crash was the moment after I submitted this on reddit, but this might really be a coincidence