You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Wrong/missing encoding of ampersands in atom/rss feeds #5
Hi,
I got an "XML Parsing Error: not well-formed" using the pluto-generated feeds available on http://blogs.openstreetmap.org/ because of a wrong re-encoding (or missing encoding) of the ampersand symbol within links/guids.
I don't know the details of that instance (version/release, environment, etc), but one of the developers suggested it should be a pluto issue.
Could you please check? Test case and details on gravitystorm/blogs.osm.org#28
(I checked past/closed issues about this but I couldn't find any)
I'm adding your original ticket / issue over here for easier reference:
I got some kind of "XML Parsing Error: not well-formed" using my favourite feedreader. I see the same error also when opening the atom/rss feeds with firefox and chromium.
It seems it's because of a wrong re-encoding (or missing encoding) of the ampersand symbol within links and guid. Example follows: (sorry it's a spam entry but I think the issue still applies)
Sorry for the long wait. I finally got around to check in detail. The error is in the feed templates (in the openstreetmap) repo that are missing xml escapes (CGI::escape_HTML) for guid and link that turns "unescaped" & back into escaped &. I will try to send in a pull request later today and than close this ticket. Again thanks for reporting the error. Keep it up. Cheers. Prosit 2020!
Activity
geraldb commentedon May 25, 2017
@unriccio Thanks for reporting. Will look into the encoding of ampersands issue. Cheers.
geraldb commentedon Jan 26, 2020
I'm adding your original ticket / issue over here for easier reference:
Note: So
%20&%20get changed to%20&%20in the guid and link tag - is this correct? Why does it break the xml parsing? Needs to get checked.unriccio commentedon Feb 3, 2020
Yep, correct.
The ampersand is used to escape entities (as indeed shown by "&"), so the parser will try to interpret "&%20" as if it was a proper entity.
geraldb commentedon Feb 3, 2020
Sorry for the long wait. I finally got around to check in detail. The error is in the feed templates (in the openstreetmap) repo that are missing xml escapes (
CGI::escape_HTML) for guid and link that turns "unescaped"&back into escaped&. I will try to send in a pull request later today and than close this ticket. Again thanks for reporting the error. Keep it up. Cheers. Prosit 2020!