Skip to content
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

Define the cookie path in config.ini.php, or in global.ini.php #1155

Closed
anonymous-matomo-user opened this issue Feb 12, 2010 · 2 comments
Closed
Labels
Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc.
Milestone

Comments

@anonymous-matomo-user
Copy link

As reported in the forum: http://forum.piwik.org/index.php?showtopic=5141, I am asking for a new feature that I can customize the cookie path, it can be in config.ini.php or in global.ini.php:


; login cookie name
login_cookie_name = piwik_auth

; login cookie expiration (30 days)
login_cookie_expire = 2592000

; login cookie path
login_cookie_path = /

By default, the piwik cookie is in "/piwik/" if I install it to /piwik folder. And there is no way for my app to read its cookie since the path is different (in this case my app is installed under /myapp/). It is very convenient for me to change it to "/" so that the cookie is accessible to all apps under the same domain.

@robocoder
Copy link
Contributor

Default behaviour should be the current, more restrictive behaviour, for backward compatibility and handling cases like www.example.com/~user1 vs www.example.com/~user2

@mattab
Copy link
Member

mattab commented Mar 16, 2010

(In [1927]) Fixes #1155 Cookie path can now be defined in config file

@anonymous-matomo-user anonymous-matomo-user added this to the Piwik 0.5.5 milestone Jul 8, 2014
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc.
Projects
None yet
Development

No branches or pull requests

3 participants