Nope, the session is specific to the server, so when you try on the second server it just won't be there... If both apps can use the same mem cache it could work? Or a cookie, which is browser side, but not to sure how the subdomain cookie accessing works...

willemwy said:

Nope, the session is specific to the server, so when you try on the second server it just won't be there... If both apps can use the same mem cache it could work? Or a cookie, which is browser side, but not to sure how the subdomain cookie accessing works...

So..anyway to get on this (how about cookie?)

Using the database session driver is probably the simplest way to make this work, assuming both subdomains run from the same database.

Or memcache / redis would also provide the same solution.