Background:
I recently found an issue on the newly released Qlik Sense June 2020 version. It had never happened on previous versions before. I believe the last version I have tried was June 2019 and there was no such problem. Also, this June 2020 instance is a new install, not upgraded from any older version. It is a single node cluster installed on Windows Server 2019 Datacenter with Active Directory configured.
Symptom:
When I do an rest API call with ticket authentication, which means there's a 'qlikTicket' param in the request, if there's a space in value of one of other params in the request I got response "HTTP Error 400. The request is badly formed.". Space character could be url encoded to "%20" or "+", either way, I got same error 400.
First time I noticed this was from QRS REST API call for getting user info:
GET https://myServer/qrs/user?xrfkey=PP4BYP8TyK4AQHi7&filter=userDirectory+eq+%27MK3%27+and+userId+eq+%27testuser%27&qlikTicket=db-ic_l4LX2c2-9U
Request has header "X-Qlik-Xrfkey: PP4BYP8TyK4AQHi7" BTW. I got 400 error.
noticed the "+" sign in "filter" param? If I removed the filter param, the response was 200 with all the users info.
Another time it happened with single integration API:
https://myServer/single/?appid=0bc3a0ed-9d71-42e0-8c43-7c550ee945b3&sheet=GnAzpy&select=clearall&theme=summer%20vibes&qlikTicket=eF4iAmzTXgbio1r
This link got 400 error because the name of theme has a space in it, notice the "%20". If I removed the "theme" param or even just change it to another theme name without space, it worked perfectly. See screenshots attached.
Like I said at the beginning, it had never happened before. In my experience, those API calls with qlikTicket authentication worked perfectly from version 3.2 to at least June 2019.
Is this a bug or could be something wrong with the instance I installed? Any suggestions?
