https://dev.to/fanreza if you have 2 apps on same domain like https://somesite.com/someapp-1 https://somesite.com/someapp-2 The CSRF token will competing each other, and it happen today in my office, the easy way to fix it is setting your cookies.php file search some settings called path in cookies.php /* |-------------------------------------------------------------------------- | Session Cookie Path |-------------------------------------------------------------------------- | | The session cookie path determines the path for which the cookie will | be regarded as available. Typically, this will be the root path of | your application but you are free to change this when necessary. | */ 'path' => '/', and change it to your app path like 'path' => '/someapp-1/' or you can use.env too thanks for reading, also thanks for this stackoverflow questions https://stackoverflow.com/questions/68468526/is-it-possible-to-rename-the-xsrf-token-cookie-that-laravel-is-creating
Newsletter

Get the latest Laravel/PHP jobs, events and curated articles straight to your inbox, once a week

Glimpse streamlines Laravel development by seamlessly deploying GitHub pull requests to preview environments with the help of Laravel Forge. Glimpse streamlines Laravel development by seamlessly deploying GitHub pull requests to preview environments with the help of Laravel Forge.
Fathom Analytics | Fast, simple and privacy-focused website analytics. Fathom Analytics | Fast, simple and privacy-focused website analytics.
Shirts painstakingly handcrafted by under-caffeinated developers. Shirts painstakingly handcrafted by under-caffeinated developers.
Community Partners