reitit 2024-12-19

Anyone has an idea why my cookie is returned to the browser as a url-encoded string? The session cookie is fine:

set-cookie:
de.bar.foo=MloVXtarzvZz7cNK%2Bri1OK0AKcDbJCcoQdg%2B%2BokPnUUQsL%2F0Hv2sZ8v8dUth5nqMbA%2FdmCbQAaiDss0JdukNQyH25%2Fh1i%2Fi33nF6ctcEFz%2BPOq9vnvb6r8vbx3PkMZHK--QV%2FG6g5xD2NIm2v76u2hojbngSj7%2BBg%2FouWBHF%2FF1t0%3D; Path=/; HttpOnly; Max-Age=86400; SameSite=Lax
the cookie-consent-cookie is bad:
set-cookie:
cookie-consent=value=accepted&path=%2F&max-age=31536000

I have the ring.middleware.cookies/wrap-cookies middleware in my middleware-chain

Have you tried adding the request response diff middleware to see where it gets garbled?

I will try that thanks

Ok, I was messing up the args, reading is king

If everyone read the manual, consultants and LLMs would be out of business 🙂 We're just creating jobs

🤣 1