frellan
11/19/2018, 8:53 AMketilsan
11/19/2018, 8:55 AMfrellan
11/19/2018, 8:55 AMdave08
11/19/2018, 9:22 AMorangy
ketilsan
11/19/2018, 9:37 AMorangy
orangy
dave08
11/19/2018, 10:48 AMFeature
that makes it opt-in to timeout a request when no reply was given. It could possibly be enabled globally or used in routing withTimeout(300) { get { ...} ... }
@orangy?orangy
dave08
11/19/2018, 11:19 AMcall.respond()
hasn't been called, I thought the request would be "waiting" around until something calls it. But it seems like I didn't notice that the original comment is that a 404 is returned...
I guess a 404 doesn't make sense in this case since a route was actually matched, so I guess I could change my proposition that there could be an opt-in Feature to “require response if matched” and similar, instead of "evil" options...?dave08
11/19/2018, 11:25 AMStatusPages
that allows catching an error that call.respond()
wasn't called?orangy
StatusPages
is actually a nice idea! May be a special unhandled
handler that will execute if response wasn’t sent…orangy
ketilsan
11/19/2018, 11:27 AMketilsan
11/19/2018, 11:27 AMketilsan
11/19/2018, 11:35 AMketilsan
11/19/2018, 11:36 AMdave08
11/19/2018, 11:38 AMketilsan
11/19/2018, 11:38 AM