-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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: allows a colon before or after an XML name #68294
Labels
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
Comments
DemiMarie
changed the title
encoding/xml: allows a colon before an XML entity name
encoding/xml: allows a colon before or after an XML name
Jul 4, 2024
This was referenced Jul 4, 2024
cagedmantis
added
the
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
label
Jul 8, 2024
Please note this related comment #68293 (comment) |
#68299 is that proposal |
This was referenced Jul 11, 2024
Open
DemiMarie
added a commit
to DemiMarie/go
that referenced
this issue
Sep 1, 2024
An XML QName is syntactically two Names separated by a colon, rather than a single name that has a colon in it. This fixes multiple bugs in XML QName reading. Fixes: golang#68294 Fixes: golang#68392 Fixes: golang#68393
Change https://go.dev/cl/609377 mentions this issue: |
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.
Go version
go version go1.21.11 linux/amd64
Output of
go env
in your module/workspace:What did you do?
https://go.dev/play/p/KE2dyxD0acX
What did you see happen?
xml.Unmarshal
accepts<:a/>
,<a:/>
,<a :b="c"/>
, and<a b:="c"/>
.What did you expect to see?
xml.Unmarshal
should return an error because<:a/>
,<a:/>
,<a :b="c"/>
, and<a b:="c"/>
are all ill-formed XML. An XML name must not start or end with a colon.The text was updated successfully, but these errors were encountered: