-
Notifications
You must be signed in to change notification settings - Fork 7
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
req.cookies is not filled #96
Comments
Is your repo maybe public or do you have a reproducible example? |
But regarding the last point: Yes, setting the cookie on the request won't do anything - it's the correct behaviour. But could maybe be made more obvious by only providing a getter - will be changed in v2. |
Hello, thanks for the quick reply ! You can look here the code in which I added my session system and used cookies : LoganTann/redbeansoup-v2@9b7ea5d If you want to run the entire repo, then use the following command line argument : You may need to create the file export default {
// Discord Developers -> Oauth2 -> Client ID
CLIENT_ID: "",
// Discord Developers -> Oauth2 -> Client secret
CLIENT_SECRET: "",
// Discord Developers -> Bot -> reset
BOT_TOKEN: "",
// Right Click on your dev server icon -> Copy ID
DEV_GUILD_ID: "",
// Get your OpenAI token in your dashboard - https://openai.com/api/
OPENAI_TOKEN: "",
WHOLESOME_ENDPOINT: "",
}; |
omg you fixed it before my reply, so fast xD thanks a lot, i'll look into that PR |
Thanks a lot for opening the issue! 🙌 Fix released with v1.3.5 |
Hello,
I'm actually creating a session system for my project. I need to read and store a session id from cookie.
Expected behavior : if the user holds a cookie with name
session
, then a controller requestingreq.cookies.session
should hold the cookie valueCurrent behavior : the object
req.cookies
is an empty object. However,req.headers.cookie
contains the raw data so a quickfix is easy.Screenshot :
Also, when I save values in req.cookie, I need to use the following code in an outgoing middleware to sync with res.cookie
The text was updated successfully, but these errors were encountered: