Hi all, I'm getting this message about a session i...

# ktor

[Hong Phuc]

Hi all, I'm getting this message about a session is found for route "/" even though I didn't have any session cookies/header in the request or explicitly call "call.sessions.get" or "call.sessions.set" on the handler. From my understanding a request comming in that doesn't have a session cookies or session header should not trigger that log, or is it the expected behaviour? Thanks in advance

2024-12-05 15:24:29.203 [eventLoopGroupProxy-4-1] TRACE io.ktor.server.sessions.Sessions - Sessions found for /: MY_SESSION
2024-12-05 15:24:29.206 [eventLoopGroupProxy-4-1] TRACE io.ktor.server.routing.Routing - Trace for []
/, segment:0 -> SUCCESS @ /
  /json, segment:0 -> FAILURE "Selector didn't match" @ /json
  /session, segment:0 -> FAILURE "Selector didn't match" @ /session
  /, segment:0 -> SUCCESS @ /
    /(method:GET), segment:0 -> SUCCESS @ /(method:GET)
Matched routes:
  "" -> "<slash>" -> "(method:GET)"
Routing resolve result:
  SUCCESS @ /(method:GET)
2024-12-05 15:24:29.211 [eventLoopGroupProxy-4-1] TRACE io.ktor.server.sessions.Sessions - Sending session data for /: MY_SESSION

Here is the code:

install(Sessions) {
    cookie<MySession>("MY_SESSION") {
        cookie.extensions["SameSite"] = "lax"
    }
}
routing {
    get("/") {
        call.respondText("Hello World!")
    }
}

[Aleksei Tirman [JB]]

Thank you for the report.