Last modified: 2014-04-28 14:33:53 UTC
it is required, to map html entities if I work with xml, or it is feature to enforce migration to json ;-) ? XML: <?xml version="1.0"?><api><query-continue><allpages apcontinue="&" /></query-continue><query><allpages>... JSON: {"query-continue":{"allpages":{"apcontinue":"&"}}," /api.php?action=query&apfrom=%26amp%3B&aplimit=...
Hi Thomas, is this a question? If so, [[mw:Project:Support_desk]] is the correct place. If you think this is a bug, please explain what the problem is that you see.
I think it's a bug, because Brad wrote in his mail "Clients should be treating the returned key-value pairs [of query-continue] as opaque data to be returned to the server with the subsequent query." I think opaque data, don't have to be parsed/interpreted (except unescapeing). The following request with url encoded '&' -> '%26amp%3B' is not okay: /api.php?action=query&apfrom=%26amp%3B... http://en.wikipedia.org/w/api.php?action=query&list=allpages&apfrom=%26amp%3B&aplimit=1 but: /api.php?action=query&apfrom=%26&... is okay btw: I don't know if only allpages is affected
This isn't a bug at all, so closing as INVALID. I'll assume it's good-faith confusion. In <allpages apcontinue="&" />, the value is the single character "&". The XML format represents it in an encoded form because a bare "&" is not allowed in XML. It could also be represented as apcontinue="&" or apcontinue="&", but in either case the actual value being represented remains unchanged. Just as in this message I'm writing this value as '"&"' even though the double-quotes are not actually part of the value, they're just there to delimit it within the running text.
silly me, & is the escaping sign
