- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 48
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
The cookie not saved after server respond with {"status": "ok"} #62
Comments
Same here, did you managed to fix it? |
Having the same issue, did you find why this happened? |
Ok so I got it working, in my case it was missing the EncryptCookies middleware in cookiesconsent.php
|
Are you on a public server? With Laravel Herd at page refresh the cookie is deleted |
I use Laravel Herd locally but I tried in my staging server too and I had the same problem. I use laravel vapor so not sure if it's specific to that maybe. |
Maybe I found an issue. I used this package in our older project and everything worked.
In our new project, the popup came back constantly and when I checked the cookie is saved at the Application tab, it is not.
I started to find differences, and I found the domain was different.
It is saved to .env in the same way, but older project (mvs) has no domain parameter in Set-Cookie.
But the newer project it has with https://.
Now I hacked the configuration file like this and it is working.
The text was updated successfully, but these errors were encountered: