Shouldn't the parameter be encoded automatically in ajax requests? Seems like this would double encode it (which should work because matomo handles it specifically, but it seems like a fix that could cause problems later). Maybe we should be urlencoding the values that can have spaces when adding the segment label?

Left a comment at #13113

@sgiehl do you maybe have an idea about how to fix #11806 which is similar?

Shouldn't the parameter be encoded automatically in ajax requests?

Yes, but then i see this code:

        // we took care of encoding &segment properly already, so we don't use $.param for it ($.param URL encodes the values)
        if(parameters['segment']) {
            url += 'segment=' + parameters['segment'] + '&';
            delete parameters['segment'];
        }

so the segment parameter is a special case/hack and not URL encoded as it's assumed by our Ajax helper that the value is already properly URL encoded. so URL encoding it manually as done in this PR is needed it seems...

hi guys, I have updated to 3.6 version a few weeks ago and I still experience this issue with URLs containing whitespaces. This is not clear if this PR is in 3.6 ? If yes so is it supposed to fix the issue ?
The Confluence URLs sent to Matomo contains initialy + (PLUS) chars. These chars are substituted with whitespaces later in Matomo. I did a very dirty workaround on the tracking client side javascript in replacing the PLUS chars with UNDERSCORE : then I am able to see the Visit Log but Confluence does not follow obviously the altered URLs. Any idea to workaround else ? Very thanks

It's supposed to work, please can you create new a issue? @eetasse

See: #13460