I'm looking at https://github.com/metosin/reitit/blob/9ae40832708bb0f5b99c738a49c7525db2f8a652/modules/reitit-ring/src/reitit/ring.cljc#L224-L225 and wondering whether it is meant to use the not-found-handler like the other branch below it? https://github.com/metosin/reitit/blob/9ae40832708bb0f5b99c738a49c7525db2f8a652/modules/reitit-ring/src/reitit/ring.cljc#L229-L230

Often nil is equivalent to {:status 404} in Ring, except if you have further middleware which adds headers to the response

Then, a map with headers but no status is implicitly treated as 200

@danielcompton not 100% sure, but the latter one is for cases where the handler is mounted inside the routing tree and the path (and method) have already matched. You actually might want to return "file not found". The first one is when it's mounted outside of the route tree, and it might be good idea to pass it on to next, e.g. redirect-trailing-slash-handler

but, is kinda inconsistent and/or not documented. Any fix would be breaking, so for 1.0.0. Ideas welcome