Encode segmentValue for Actions reports. This extra encoding is required because of how many times a segment is urldecoded:
This means the value needs to be triple encoded for values like plus signs to be used properly in the segment.
http://example.org/with+plus/will display like that, instead of
I am not sure if this fix will have repercussions so I haven't modified the tests. Will do so after someone else gives their opinion.
If it fixes your issue and tests pass probably all good to go. It's almost impossible to review it since the segments are just a mess and we never know where they are urlencoded or urldecoded etc.
It will change a lot of the test output I think (another encoding in the segment property in API output). Think this won't be a BC break? at least not a potentially huge one.
Think this won't be a BC break?
I really don't know. As long as we can still handle the segments urlencoded and urldecoded it should be fine.
Applied the patch locally and it resolves the issue for me.