You can extends the default VerifyCsrfToken middleware and overwrite the functions that are pointed out in that issue to use another cookie name.
That middleware can be placed on your routes in stead of the default version.
Sign in to participate in this thread!
We'd like to thank these amazing companies for supporting us
The Laravel portal for problem solving, knowledge sharing and community building.