Hi
Thanks for reporting this. I’ve been checking the code and I can confirm that the way we are decoding the filter does not have into account encoded chars. However, I wonder if this is something we want to improve or not, so I’ll talk about it with the team.
Can I ask what is that http client you are using to make the calls?
Is it intended behaviour of resin backend or a bug
This is the intended behaviour. Only single and double quotes, + and a couple other characters need to be encoded. If there is an option to use our SDK(s) or pinejs-client, all of the encoding is handled automatically.