The Data Is Not Legal for a Jdom Character Content
In addition, I discovered that you can specify the contentType in an ajax call CONFSERVER-15569 Breaking some Unicode characters in a page RSS feed The XML 1.0 specification does not allow you to use the 0x1a character. never. It`s not a Unicode character Anyway, I suspect you have a problem in your code between the input field and the setAttribute JDOM. Have a call. Is there anything between these places that changes the character encoding, serialization, or any other change in the input value? I guess there`s another issue before calling JDOM that changes the data, as it`s unlikely you`re really trying to load the character 0x1a as an XML character. The XML 1.1 specification allows 0x1a characters, I see: www.w3.org/TR/2004/REC-xml11-20040204/#NT-Char We can see that the browser encoding comes from the Unicode code point for these two characters: The CONFSERVER-13285 Axis web service may be prompted to submit invalid XML characters The feed URL is extranet.atlassian.com/createrssfeed.action?types=page&types=blogpost&types=mail&types=comment&sort=modified&showContent=true&showDiff=true&spaces=conf_favorites&spaces=conf_personal&labelString=&rssType=atom&maxResults=50&timeSpan=10&publicFeed=false&title=EAC+feed&os_authType=basic If you`re already patched at this level, it`s probably something else. I switched from the jQuery URLEncode plugin to the native javascript function: www.w3.org/TR/2008/PER-xml-20080205/#charsets As @rolfl suspect, something is very strange in your browser. What do you use? @alligator, thank you for the contribution! I found a form ID (5186) for this issue. Is this an Ajax javascript library you use? Maybe it`s time for a change? If we do a bit of Unicode and coding detective work, we can get a clue as to what`s probably going on. I suggest opening a support case and sharing the number here so I can follow it accordingly.
