Escape character for Session relevance

Usage and Config Platform
1

I am trying to query fixlet ID by fixlet name . Unfortunately fixlet name has double quotes in name. Hence session relevance is failing -
relevance- (id of it) of bes fixlets whose (name of it = "fixletname")

In case of fixletname contains double quotes , this relevance fails .

I tried replacing double quotes by %22 or %2522.
Every time it get replaced by " .

I am executing query using -
http://iemserver:52311/api/query?relevance=(id of it) of bes fixlets whose (name of it = "fixletname")

This is failing-
http://iemserver:52311/api/query?relevance=(id of it) of bes fixlets whose (name of it = "fixlet%22na%22me")
http://iemserver:52311/api/query?relevance=(id of it) of bes fixlets whose (name of it = "fixlet%2522na%2522me")

2

Hi @Sidd

I remembered a post that has the same, so did a little digging:

Here they use %252522 … You can try that? Now idea why it should be that, but give it a try :slight_smile:

2 Likes
3

It’s an example of doubling-up on the escape sequences, when the escape codes will be evaluated more than once.

(name of it) of bes fixlets whose (relevance of it as lowercase contains "name of operating system as lowercase contains %252522win%252522")

First pass, (probably at the client), Relevance Substitution converts “%25” to “%” (25 is the hexadecimal of the ASCII code for a percent symbol). So you end up with “%2522win%2522”, where the remaining “25” strings are the second 25’s in each sequence.

Second pass (probably at the server), “%2522win%2522” is evaluated as “%22win%22” (again, “%25” is translated to the percent symbol “%”.

In a third pass, “%2522win%2522” will be translated to “%22win%22”.

Finally, “%22” is the escape code for a double-quote character.

…not saying this will work, just trying to help visualize why multiple %252522 codes might be helpful.

4 Likes
4

Thats working !!! I was almost on same path , just missed extra 25 for second pass at server side.

2 Likes
5

Glad it worked. It was a super pain to figure out the first time.

Also, thanks for the explanation @JasonWalker … I’d say you are right, though I’m not exactly sure where all of the layers are that are interpreting the escaped characters.