4 ms·
Here's a cookie set in my browser from github in a fresh browser: Cookie: _gh_sess=eAAHHEQEjZlQKwq8kaSMpTeHC7tyMGwhVexbpZMVfDbjWCf764z4UMG7S%2FeLZpE0ML5y8%2Fnm
by etaioinshrdlu 6y ago
Here's a cookie set in my browser from github in a fresh browser: Cookie:
_gh_sess=eAAHHEQEjZlQKwq8kaSMpTeHC7tyMGwhVexbpZMVfDbjWCf764z4UMG7S%2FeLZpE0ML5y8%2FnmSEd2ZhiDLBHlZyA08Dj8cGob%2BGXSbGSjztMyc5pdd8uxj8qgxc78SHYw01E6pnOnWHRo7XoeTjKje%2FktOx5wObpjZj8JhfOnngdIlhfxSc1EctIth6RDFIsr2HPw9pbDczMfDwwKuswMrkMIt1JEOglF2L%2BxAdscMjeuXu2zFei58AR%2FwRQ%2FGgY3RbQigWt2w%2BKHDIY7a6pISw%3D%3D--H9M6LNV7YPDc1Dvm--vbgFN9CpCkCxTdfhdlvJkg%3D%3D; _octo=GH1.1.770191202.1608243985; logged_in=no; tz=America%2FLos_Angeles
This could easily be used for tracking on the backend... It would be better to not store a large opaque string.
- slig 6y agoHow is that opaque string any different than any shorter, random string that uniquely identifies the user such as "da39a3ee5e6b4b0d3255bfef95601890afd80709"? They can store whatever data they want in the session store in the backend.
- etaioinshrdlu 6y agoThey could just store certain variables explicitly like they do for these ones: logged_in=no; tz=America%2FLos_Angeles It could get rather big of course. They could not store sessions on the backend for anonymous users.