Navigation Menu

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

Make Piwik opt-out feature work on safari and internet explorer #3135

Closed
ryrun opened this issue May 3, 2012 · 15 comments
Closed

Make Piwik opt-out feature work on safari and internet explorer #3135

ryrun opened this issue May 3, 2012 · 15 comments
Assignees
Labels
c: Privacy For issues that impact or improve the privacy. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.
Milestone

Comments

@ryrun
Copy link

ryrun commented May 3, 2012

Iframe dont work with internet explorer and safari, when piwik is hosted on a different domain. Its not possible to uncheck the checkbox. Browser wont set the needed cookie.

Solution for IE:
Add following to your .htaccess(create one, when needed) in your piwik folder:
header append P3P "CP="CAO PSA OUR"" (thx to MuX512 for this)

Maybe the iframe could send this via php:
header('P3P: CP="CAO PSA OUR"');

For Safari we need another method to set the cookie:
Safari block every cookie from pages, which wasn't "clicked"/opened from user.

German forum thread about this:
http://forum.piwik.org/read.php?5,71496

Tested some suggestions, the "_top" method dont work for safari ...

@mattab
Copy link
Member

mattab commented May 7, 2012

Is there a solution that work in the thread?

@ryrun
Copy link
Author

ryrun commented May 8, 2012

There is currently no working solution in the thread for safari. The user needs to open the iframe url directly, then its possible to set a cookie. I'm not sure, how you can implement this. Maybe as extra button?

@mattab
Copy link
Member

mattab commented Jan 13, 2014

See also #2930

@anonymous-matomo-user
Copy link

Same problem applies when using Puffin trying to opt out (browser from the apple store using a user agent).

Am I doing something wrong here? I created a .htaccess simply including header append P3P "CP="CAO PSA OUR"" and nothing else, that doesn't work. Putting header('P3P: CP="CAO PSA OUR"'); into index.php (just below the use commands) doesn't do the job for me either... did I misunderstand something there?
This solution partly works for puffin though (the .htaccess one), as I can now unhook in the iframe. Yet it still shows any activity in piwik when using this browser...

@mattab
Copy link
Member

mattab commented Feb 3, 2014

I believe the problem "may" be that these browsers don't accept third party cookies, and that opt-out iframe works by setting an "opt-out" cookie which is third party.

(as opposed to our other tracking cookies which are first party).

Not sure what the best solution would be, to have opt-out work on all browsers?
How could we make the iframe work for all browsers?

@mattab
Copy link
Member

mattab commented Mar 16, 2014

Another solution would be to add the opt-out feature to the Piwik tracker itself. eg. Piwik.showOptOutMessage()

A website operator could be put this code in the Privacy Policy page, or other places. This would show a message with a checkbox, letting visitors know whether they are tracked or not. A visitor is not tracked if he has the first party cookie "donottrack" or if DoNotTrack feature is enabled in browser. Visitor can click on checkbox to set a first party cookie "donottrack" which will exclude them from tracking.

The disadvantage of first party cookies is that tracking will be enabled only on this website and not all websites within Piwik.

@ryrun ryrun added this to the 2.x - The Great Piwik 2.x Backlog milestone Jul 8, 2014
@mattab
Copy link
Member

mattab commented Jul 26, 2014

A new idea was suggested: make opt-out iframe redirect to piwik server, set the cookie, then silently redirect back to the page where the opt-out iframe was included. Maybe in this case the opt-out cookie would be properly set?

@mattab mattab modified the milestones: Piwik 2.5.0, The Great Piwik 2.x Backlog Jul 26, 2014
@ryrun
Copy link
Author

ryrun commented Jul 26, 2014

This could work. Not sure how a silent redirect will be implemented. Maybe as blank page with a redirect in the meta data? The form in the Opt-out frame could use "_top", so the whole tab is loading the piwik server page.

@mattab
Copy link
Member

mattab commented Aug 3, 2014

@ryrun good idea to use _"top" so the iframe simply redirects the whole page back, this would make a smooth user experience.

@alex-gulentz
Copy link

Hey Guys,

the most important features of Piwik are: Privacy protection and complaint with the privacy regulation of the European Union. The opt-out is a very important feature there, because the opt-out is requested i.e. by the German law!

I would like to ask you to increase the importance of this Issue and start solving this.

Can this be possible?

Br, Alex

@diosmosis diosmosis self-assigned this Apr 20, 2015
@diosmosis
Copy link
Member

After some testing, everything appears to work on IE7/8/9. I can confirm it's broken for Safari.

@alex-gulentz
Copy link

Is there any timeline when this Issue will be solved? It is very important!
@mattab could you schedule this fix?

@diosmosis
Copy link
Member

It is scheduled for 2.14.0 (as you can see in the Milestone section on the right). I've assigned myself to fix it.

diosmosis pushed a commit that referenced this issue Apr 23, 2015
@Cruiser13
Copy link

This issue does still exist for me with Piwik 2.14.3 and Internet Explorer 11 if third party cookies are disabled.
The optout checkbox will stay checked even if I click on it.

@mattab
Copy link
Member

mattab commented Aug 14, 2015

@Cruiser13 thanks for the report. Created an issue: #8578

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c: Privacy For issues that impact or improve the privacy. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.
Projects
None yet
Development

No branches or pull requests

6 participants