-
-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ULID cookie #577
Projects
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It's useful to track requests against their sessions, to track down issues or monitor real world usage. This is where something like Google Analytics is usually used, but that requires cross-domain cookies, which is extremely bad for user privacy, so requires annoying cookie popups by law.
All of the required analytical functionality can be achieved by setting a ULID cookie. Even though there's no cross domain cookies involved, this should still be opt-in by the developer.
In
config.default.ini
, setapp.unique_cookie=
to disable by default, but if any value is set here it will be used as the cookie name. Settingapp.unique_cookie=ulid
.This will allow logs to be made with the appropriate ULID, and nginx can store this ULID in the access log for general usage analytics.
The text was updated successfully, but these errors were encountered: