+1000 Why would anything break because of this? My feed is served over HTTPS.
If nothing else the warning text is absolutely incoherent in 2016 where HTTPS is if anything the new standard for delivering anything.
If you're going to obey an out of date spec you should add an explanation to the warning so people don't go crazy. You need to teach us how silly the spec is.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is due to the RSS spec; see here for details:
https://groups.google.com/d/msg/feedvalidator-users/1UQ7nUWRSN0/HqP9TdTq46wJ
The law is the law, I know :)
However, mentioning the URL scheme in that sentence really looks like an accidental over-specification.
Any chance that feedvalidator could relax this requirement?
Maybe demoting this to an interoperability warning?
+1000 Why would anything break because of this? My feed is served over HTTPS.
If nothing else the warning text is absolutely incoherent in 2016 where HTTPS is if anything the new standard for delivering anything.
If you're going to obey an out of date spec you should add an explanation to the warning so people don't go crazy. You need to teach us how silly the spec is.