-
Notifications
You must be signed in to change notification settings - Fork 43
CDATA content incorrectly encoded in version 0.90.x #304
Copy link
Copy link
Closed
Labels
indevThe issue is fixed/implemented in the dev branchThe issue is fixed/implemented in the dev branch
Description
In version 0.90.x, strings inside <![CDATA[ ... ]]> are being encoded, which should not happen.
The content of a CDATA section is supposed to be treated as raw text and preserved as-is, without escaping characters like &.
Example:
Expected:
<![CDATA[?param1=value1¶m2=value2]]>
Actual:
<![CDATA[?param1=value1&param2=value2]]>
This breaks interoperability with systems expecting the original unescaped string inside CDATA sections.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
indevThe issue is fixed/implemented in the dev branchThe issue is fixed/implemented in the dev branch