Segmented visitor log export fails due to lack of token_auth #10147

2.16.0 Scenario reproduced on Chrome:

1. Go to Actions->Events
2. Open segmented visitor log for some event
3. Scroll down
4. Open export bar
5. TSV link is in scope here. If you right-click it, you will get something like:

https://domain.com/index.php?module=API&method=Live.getLastVisitsDetails&format=TSV&idSite=4&period=day&date=2016-05-10&expanded=1&translateColumnNames=1&language=en&segment=eventCategory==Some_value

1. So, copying such a link and pasting it in new tab causes message about lack of permissions, because it's missing token_auth parameter.
2. Now just click this link, allow the file to download.
3. Now, if you right click it and use "Copy link address", you will get the same link but enhanced with token_auth and filter_limit:

https://domain.com/index.php?module=API&method=Live.getLastVisitsDetails&format=TSV&idSite=4&period=day&date=2016-05-10&expanded=1&translateColumnNames=1&language=en&segment=eventCategory==Some_value&token_auth=token_auth_here&filter_limit=20

1. Now such link will work if copied and pasted in another window. Cool. But here comes the fun part:
2. Just click the link once again and allow file to be downloaded once again.
3. Right click the link and copy it now. Now, it willhave token_auth and filter_limit added 2 times. This can go on and on.

Basic issue is that after first entering of the segmented visitor log, right-clicked copied link doesn't work straight away. But I see there is some bigger problem connected with that and I believe it may be generic to all segmented visitor logs view or maybe some more reports which can be exported.

This is currently expected behaviour and was added because of https://github.com/piwik/piwik/issues/2701 in https://github.com/piwik/piwik/commit/7f0793738b0c3d94135b852b63b1ec6e5284091e by the looks. This should be the behaviour for all of our export links no matter where.

Maybe we could also listen on right click and modify the link in such a case. I presume there should not be any risk for it

Thanks @tsteur for clearing it out, now I understand. Are you aiming to fix it in next version?

Probably not as it's not a critical bug that could lead to data loss or something. This would be usually more like something for mid term as it still works in general

The new "Copy Export URL" feature was introduced recently fixing this issue.