Ampersand (&) not encoded in parameter value

[JensRoggenstein]

Describe the bug
When I define a query parameter value which contains an ampersand, the query value is split to a second query parameter instead of encoding all characters.

Steps to reproduce

• Create a request
• Add a query parameter with key "filters" and value "item.id==123&item.type==bug"
• The generated query string is ?filters=item.id%3D%3D123&item.type=%3Dbug

Expected behavior

• The query parameter value should be completely URL encoded instead of creating a second query parameter
• The generated query string should be ?filters=item.id%3D%3D123%26item.type%3D%3Dbug

It is currently not possible to send the request with JetClient as expected from the backend. Either the ampersand is not encoded, which splits the parameter value to a second query parameter, or it is double encoded if I encode it as %26 in the parameter value field.

Environment information:

• plugin version: 2024.3.26-243

[AntonShuvaev]

Thanks for reporting the issue. As a workaround, you can disable Encode URL automatically in the folder settings and manually encode & as %26. I will add automatic encoding for parameter values in the next version.

[AntonShuvaev]

I've fixed the issue. Now, when you write $ or # in the query parameter table, it is encoded. To prevent double encoding, you need to disable "Encode URL automatically" in the folder settings.

[JensRoggenstein]

Thanks, Anton, this workaround solves our issue. 👍