@acalbazana
Thank you for clarifying. This is now reproducible in my environment.
I have also picked up the new case you opened so we can work through this.
RFC1738 designates the pipe as an unsafe (though supported) character in a URL.
It looks like we can probably work around this by URL encoding the query parameters. I will do some testing today and reach out so we can work on it further.
Regards,
Joe