Hacker News Reader

Comment by muloka | Hacker News Reader

I imagine this could this be used to kill a running instance of node.js in production?

No, it won't kill the process; it will simply terminate the connection. It looks like, from the C code, that it was intended to throw a 405 but somewhere in the process it screws up and terminates early.

Ah thanks for clearing that up.

How?

maybe something like:

    curl -v -s -X "GE$(printf '%.s ' {0..100000})" localhost:8888

It doesn't kill node process.. but there could be buffer overflow or similar bug in that parser code.

Reply on news.ycombinator.com