Why laravel 5.4 different levels of addresses produce different session?

Development environment:
front and back end two sets of user systems:
background homepage is: http://www.mysite.com/admin/
background login page: http://www.mysite.com/admin/l.
merchandise management page: http://www.mysite.com/admin/m.
user Management Page: http://www.mysite.com/admin/user
can jump to the login page normally when I visit http://www.mysite.com/admin. Jump back to / admin; after successful login

question:
when you access http://www.mysite.com/admin/m. in an unlogged state, it automatically jumps to the login page and still jumps to / admin, after successful login. At this time, you are actually logged in. Continuing to enter http://www.mysite.com/admin/m. access will still jump to / admin.

clues that have been checked out:
1, when visiting: http://www.mysite.com/admin/m., session (named session1)
2 is generated, middleware verification finds that it is not logged in, jumps to the login page, at this time a new session (named session2)
3 is generated, login is performed, session (named session3) is generated after successful login, and session2 is destroyed.
4. When you visit http://www.mysite.com/admin/m. again at this time, the program gets session1, verification and does not log in and jumps to the login page. The login page successfully jumps back to the background home page / admin using session3 verification. As a result, the merchandise management page can never be accessed.

when accessing the user management page, it is successful, and this is not the case.
currently troubleshoot different levels of access paths (routes) resulting in different session resulting in inconsistent login status. I hope all the gods will give us some advice.

Apr.22,2021

has found the problem. There is a variable path, in the configuration file of
session. This path is configured as an absolute path based on windows (555555). In this case, laravel cannot recognize the location of cookies storage and stores it by access address, so different cookies, is used when accessing / admin/mall/product and / admin/login, that is, multiple session need to be generated.

solution: configuring path to "/" leaves only one session

'path' => '/',

this is possible if you use your own Auth, for login authentication.
Auth is divided into guard, and guard is used to solve the login of different account systems at the front and back end.
see if you are using a different guard.

Menu