Ktor Version and Engine Used (client or server and name)
1.2.5 and 1.3.0-beta-1, server, netty and CIO
Describe the bug
When using the base64 encoding for a session cookie, the correct cookie is not picked up.
In my repro example below I am basically calling /login, which sets the session, and then /, where the session is evaluated. When using base64 encoding, the second call doesn't succeed, as no session is found.
Important to notice that this works with all other encodings, and even with base64 in the test engine.
Ktor Version and Engine Used (client or server and name) 1.2.5 and 1.3.0-beta-1, server, netty and CIO
Describe the bug When using the base64 encoding for a session cookie, the correct cookie is not picked up.
In my repro example below I am basically calling
/login
, which sets the session, and then/
, where the session is evaluated. When using base64 encoding, the second call doesn't succeed, as no session is found.Important to notice that this works with all other encodings, and even with base64 in the test engine.
To Reproduce Minimal repro here: https://github.com/AndreasVolkmann/ktor-session
Steps to reproduce the behavior:
localhost:5000/login
which should returnLogged in
and set the session / cookie.localhost:5000
where an error is shownWhen changing the encoding, the above scenario works.
Expected behavior The session cookie should be set and valid for the next call, just like with all other encodings and under test.
Tested with multiple browsers and postman.