You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The XSRF-TOKEN should be attached to the response when calling the drip endpoint.
Actual Behavior
No cookies are attached to the drip response when route caching is enabled. This is due to the fact that the drip route is not linked with the ‘web’ middleware group which add the cookie via the VerifyCRSF middleware. I think this is caused by the way the route are added in the ServiceProvider which is not compatible with route caching. Desactivating route caching in production solves the issue
Environment
PHP Version: 8.2
Laravel Version: 10.48.12
LaravelCaffeine Version: 10.0.2
Stack Trace
The text was updated successfully, but these errors were encountered:
@michellaurent Thank you for reporting this. I'm not sure how soon I will be able to look into this, so if you are able to submit a PR with proposed changes, that would greatly help.
There is a check in Providers\Service.php to determine if the routes has to be loaded in the web middleware group or not. I think that this check fails when routes are cached.
Expected Behavior
The XSRF-TOKEN should be attached to the response when calling the drip endpoint.
Actual Behavior
No cookies are attached to the drip response when route caching is enabled. This is due to the fact that the drip route is not linked with the ‘web’ middleware group which add the cookie via the VerifyCRSF middleware. I think this is caused by the way the route are added in the ServiceProvider which is not compatible with route caching. Desactivating route caching in production solves the issue
Environment
Stack Trace
The text was updated successfully, but these errors were encountered: