aboutsummaryrefslogtreecommitdiffstats
path: root/src/cowboy_router.erl
diff options
context:
space:
mode:
authorLoïc Hoguin <[email protected]>2013-08-24 20:36:23 +0200
committerLoïc Hoguin <[email protected]>2013-08-24 20:36:23 +0200
commitbbee34fe1638b742796b00b39c0859395a752167 (patch)
tree206ea48ff473d98d7de39435c52fca1f24c66ee1 /src/cowboy_router.erl
parent694c9bfbfae461550691e1e48c5046b52f7aca27 (diff)
downloadcowboy-bbee34fe1638b742796b00b39c0859395a752167.tar.gz
cowboy-bbee34fe1638b742796b00b39c0859395a752167.tar.bz2
cowboy-bbee34fe1638b742796b00b39c0859395a752167.zip
Crash on failure, don't report errors
When something went wrong in a handler we used to report errors and then terminate the process normally. This doesn't work so well with links which won't detect failure. Now we still catch the error, but throw another one with more details on why it happened, including the Req object information and the stacktrace. Ranch will then print an error message with all this information. Because we crash directly, this also means that we will not hog resources unnecessarily for too long when something bad happens.
Diffstat (limited to 'src/cowboy_router.erl')
0 files changed, 0 insertions, 0 deletions