-
Notifications
You must be signed in to change notification settings - Fork 17.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
encoding/xml: CDATA section allows invalid characters #53728
Labels
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Comments
cc @rsc |
This is a general issue, not just with cdata:
|
looks like this old commit did the breakage f74eb6d#diff-0526795219b1a2003e16773ef66844f384410205af46abac3edd309b22b88aeeR704-R705 as a fix to #4235 |
my expectation would be that \x1b gets encoded to |
This was referenced Jul 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
A simple
main.go
program:Run and store the output:
Try validate the xml:
What did you expect to see?
encode error, or
no error with invalid character being replaced
What did you see instead?
encode success, but xmllint report parse error
Reference:
The text was updated successfully, but these errors were encountered: