4 ms·
Feed Validator is one. (It returns “href must be a valid URL” for image resources that start https:// https:// because the RSS spec does not openly say that HTT
by modernerd 9y ago
Feed Validator is one. (It returns “href must be a valid URL” for image resources that start https:// https:// because the RSS spec does not openly say that HTTPS image URLs are valid.)
I tried and failed to change this, and was told that the RSS spec needed to change first:
https://github.com/rubys/feedvalidator/issues/16 https://github.com/rubys/feedvalidator/issues/16
And I'm not the only one:
https://github.com/rubys/feedvalidator/pull/30 https://github.com/rubys/feedvalidator/pull/30
I respect Sam's opinion in those threads because really the spec needs to change, but I've given up trying to change it.
We ended up serving all feed URLs over HTTP as a result because customers using Feed Validator kept complaining that our product generated invalid feeds.
- grzm 9y agoThanks for the links. Do you happen to know if the validator accepts Atom with https resources? I'd think it should (if I'm understanding correctly), given that it uses IRIs, and IRIs support https as a protocol.
- modernerd 9y agoYes, it seems to validate Atom feeds with HTTPS image sources: http://www.feedvalidator.org/check.cgi?url=http%3A%2F%2Ftantek.com%2Fupdates.atom http://www.feedvalidator.org/check.cgi?url=http%3A%2F%2Ftant... Apple no longer supports Atom for podcasts, though, so unfortunately we couldn't use it as an alternative. (Podcast feeds must now be RSS 2.0: https://help.apple.com/itc/podcasts_connect/#/itc1723472cb https://help.apple.com/itc/podcasts_connect/#/itc1723472cb )