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

Jump to bottom

how en encrypt url params of matomo.php from inside matomo.js #16334

Closed
ghost opened this issue Aug 21, 2020 · 2 comments
Closed

how en encrypt url params of matomo.php from inside matomo.js #16334

ghost opened this issue Aug 21, 2020 · 2 comments
Labels
duplicate For issues that already existed in our issue tracker and were reported previously.

Comments

@ghost
Copy link

ghost commented Aug 21, 2020

My goal is to encrypt the url params then send the matomo.php request to a proxy, which will decrypt the params and then send to the real matomo.php. The reason for this is I am already proxying matomo.php and matomo.js with different file names and from the same domain but ublock stills blocks it. I'm thinking it identifies the url params?

Inside matomo.js https://raw.githubusercontent.com/matomo-org/matomo/master/js/piwik.js where should I be encrypting the request? I see 2 request types, XMLRequest and sendBacon, which one should I use? Is there a central place where I can encrypt the request query string?
@sgiehl
Copy link
Member

sgiehl commented Aug 21, 2020

Guess you mean something like this: https://github.com/matomo-org/matomo/pull/14211/files
It's a bit older approach, but should still work that way I think

@tsteur
Copy link
Member

tsteur commented Aug 23, 2020

Thanks for creating this issue @dave-dm . I'll close this issue as a duplicate of #7364 and #14207

@tsteur tsteur closed this as completed Aug 23, 2020
@tsteur tsteur added the duplicate For issues that already existed in our issue tracker and were reported previously. label Aug 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
duplicate For issues that already existed in our issue tracker and were reported previously.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tsteur @sgiehl