Hey does anyone know why whenever an invalid route is passed to the API StatusPages sends the reques...

# ktor

[Tech]

Hey does anyone know why whenever an invalid route is passed to the API StatusPages sends the request back twice?
Checking if it was sent/committed doesn't resolve the issue.

[Tech]

I fixed it by adding a wild card route at the top of my routing {} scope and simply throwing a not found exception.

When an invalid route is used it automatically returns HTTP 404 then my statuses block in StatusPages also picks it up which sends back two HTTP requests in the pipeline (to my understanding)

route("{...}") {
            handle { throw ResourceNotFoundException() }
        }

[Aleksei Tirman [JB]]

Can you share the complete code snippet?

[Tech]

For what's causing the double call respond?

[Aleksei Tirman [JB]]

I cannot reproduce your problem with the following code:

embeddedServer(Netty, port = 8082) {
    install(StatusPages) {
        status(HttpStatusCode.NotFound) { call, _ ->
            call.respondText { "NOT FOUND" }
        }
    }

    routing {

    }
}.start(true)

[Aleksei Tirman [JB]]

And by making a <http://localhost:8082/test> request.

[Tech]

Do you have call monitoring set up?
When I’m available I’ll set up a repository

[Aleksei Tirman [JB]]

It seems to be a buggy behavior. I've created an issue to address it.

[Tech]

Gotcha, appreciate it

[Tech]

I'm not exactly sure if it's actually sending the request back twice or just logging it twice.
I've had instances where the response times were different which makes me believe two requests are being sent back

[Alex J.]

if it is listener/subscriber based there is a bug related to dev mode