I’m seeing some behavior in Magento 2’s cookie management that has my “I’ve been at this too long” hackles raised.
- Different areas (
adminhtml
,frontend
) still have separate session cookies, but theadminhtml
area’s is namedadmin
, and the frontend area’s uses the defaultPHPSESSID
. It’s unclear is the sessions are actually tie to areas though (needs more investigating) - I’m seeing cookies created with both the
.example.com
andexample.com
domain name within a single area -
The admin session cookies seems to actually use the “path” parameter
Magento 1’s cookie naming wasn’t my favorite – the explicit domain name thing has been a problem for a while, but Magento 2’s seem a step back. I anticipate small pain in the behind bugs when dealing with extensions that use cookies, as well as integrating proxy services like CloudFlare that rely on setting cookies.