https://validator.w3.org/feed/check.cgi?url=https://fedoramagazine.org/
Sorry This feed does not validate. line 121, column 115: XML parsing error: <unknown>:121:115: not well-formed (invalid token) [help] ... s/2016/10/f25-beta.jpg?fit=300%2C127&ssl=1" length="132612" type="image/ ... ^ In addition, interoperability with the widest range of feed readers could be improved by implementing the following recommendation. line 118, column 3: content:encoded should not contain relative URL references: #Fedora_Atomic [help] ]]></content:encoded> ^ Source: https://fedoramagazine.org/feed/
@puiterwijk @pfrields @ryanlerch Any ideas on this one?
I double-checked this now, and it seems like a lot of the errors being thrown are related to images hosted on the CDN. We're troubleshooting an issue with images now, so I'm not sure if it's related to some of the failures found in the RSS validation. I would like to try to get to the bottom of this once we clear up any remaining issues with our CDN.
okies, the issue with the feed here is that that url has the & in it, but not in a cdata block, or using an xml entity (&).
Since this the is CDN that is putting this in here, not sure what to do to fix this.
--ry
Is the WP engine and or the CDN doing hsts instead of proper full SSL? the Url string marker seems to indicate it is asking for a delayed SSL connect (i.e. HTTP >301 > https ) and that syntax, as Ryan stated is failing to use XML or cdata syntax and throwing the errors.
And to the secondary error (line 118 one) that is a valid internal redirect error I can look at it later this weekend but fear I will have insufficient access to the host(s) to make the changes so I'll likely just PR it here.
@ryanlerch To follow up on this, is this an issue we would want to communicate with our CDN or is it something @puiterwijk could help with?
Hi all, is this blocking the use of the RSS feed for anyone reading the Magazine? If it's not interfering with how the RSS feed is actually displayed and rendered, I think we can close this ticket since the issue isn't something we can (easily) fix (with regards to Ryan's comment on it being an issue with our CDN).
Metadata Update from @jflory7: - Issue set to the milestone: None (was: Fedora 26)
Metadata Update from @jflory7: - Issue set to the milestone: Fedora 27 (to Nov. 2017)
Metadata Update from @jflory7: - Issue tagged with: needs feedback
I've never personally experienced any issues, but making sure the content passes W3C validation is just good practice. Feel free to close if there haven't been any reports.
@viorel Thanks for the follow-up. For now, I'm going to close this, but if it ever does become a breaking issue, we can try to dig deeper with our CDN provider.
Metadata Update from @jflory7: - Issue close_status updated to: Insufficient data - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.