Loading Profile...
API ASCII control codes (0-31) in returned XML.
When I get the issues for one of my projects it somehow contains ASCII control codes which invalidates the XML. It only happens on one issue in the issue list ( i bet it's in the description damn those pesky contentEditable divs! :p) for one project but perhaps the API could always strip the end result of any ASCII control codes ?
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?This is interesting as the XML conversion is done automatically by the library, so I assumed it would be sanitised. I reckon converting it to CDATA should solve the problem although I am not sure if even then control codes as acceptable?
EMPLOYEE
