-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make signed cookies work or default to non-signed #51
Labels
Comments
Hi, glad to hear that Macchiato came in handy. And the issue definitely does looks like a bug. I completely agree that the session should work with signed cookies. This would probably be the place to look. I might not have a chance to investigate in the near future, but if you'd be up for poking around I could definitely help getting a PR in and doing a release. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
First and foremost: The world needs something like Macchiato and I've used for several projects by now: thanks for making it work!
Now for my issue ;) …
Using the current template and following the current Documentation, cookies set “by hand” show up as `nil´ in subsequent request. Consider the following server config:
“mycookie” is sucessfully set in the browser, but subsequent requests show
{"macchiato-session" {:value "G__1"}, "macchiato-session.sig" {:value nil}, "mycookie" {:value nil}}
.In order to
assoc
cookies as described in the documentation, it seems one has to use unsigned cookies and thus add:cookies {:signed? false}
to the server configuration. I feel this should at least be part of the documentation and template.Even better would be knowing how to actually make macchiato work with signed cookies… I assume it's possible given the option for it but haven't figured out how… any clues?
The text was updated successfully, but these errors were encountered: