You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There were some changes recently to protect data being passed through clixon from being misinterpreted as XML and breaking the parser (thanks for that).
We are still having problems because you need to keep track of whether a string has been encoded or decoded already - for example if I start with the string "%" and using URI encoding the encoded result is "%25" if that gets encoded again, I get "%2525" and when I'm decoding I have no way to tell whether the original was "%25" or "%"... (the same thing can happen with XML encoding too)
We believe that the best way to deal with this is to use CDATA - which essentially "quotes" the data and tells the parser to skip on to the end marker. There's no laborious or inefficient en/decoding and we can pass it through as many time as we like and it's not altered.
So, we're requesting you implement CDATA in clixon,
thanks
The text was updated successfully, but these errors were encountered:
There were some changes recently to protect data being passed through clixon from being misinterpreted as XML and breaking the parser (thanks for that).
We are still having problems because you need to keep track of whether a string has been encoded or decoded already - for example if I start with the string "%" and using URI encoding the encoded result is "%25" if that gets encoded again, I get "%2525" and when I'm decoding I have no way to tell whether the original was "%25" or "%"... (the same thing can happen with XML encoding too)
We believe that the best way to deal with this is to use CDATA - which essentially "quotes" the data and tells the parser to skip on to the end marker. There's no laborious or inefficient en/decoding and we can pass it through as many time as we like and it's not altered.
So, we're requesting you implement CDATA in clixon,
thanks
The text was updated successfully, but these errors were encountered: