"lost in ambiguity tie" sounds like maybe there is another route that matches too, so it doesn't kno...

# ktor

[Leon K]

"lost in ambiguity tie" sounds like maybe there is another route that matches too, so it doesn't know what to do?

[emil]

good idea, for debugging porpuses I removed all other routes. The result is

2020-02-23 12:04:06.748 [nioEventLoopGroup-4-1] TRACE Application - Trace for [joinGame, fasd234r]
/, segment:0 -> SUCCESS; Parameters [gameId=[fasd234r]] @ /joinGame/{gameId}/(method:GET))
  /joinGame, segment:1 -> SUCCESS; Parameters [gameId=[fasd234r]] @ /joinGame/{gameId}/(method:GET))
    /joinGame/{gameId}, segment:2 -> SUCCESS @ /joinGame/{gameId}/(method:GET))
      /joinGame/{gameId}/(method:GET), segment:2 -> SUCCESS @ /joinGame/{gameId}/(method:GET))

2020-02-23 12:04:06.780 [nioEventLoopGroup-4-1] INFO  Application - Unhandled: GET - /joinGame/fasd234r

which confuses me even more

[cy]

Looks like you have no response in your handler

[emil]

Jep, thank you. I messed up some branching logic