The Feed Validator clearly isn't updated with the new Daylight Saving
dates, since it comes up with "implausible date" for every feed I
test... Time to update the date of the server guys ;)
On Tue, Mar 18, 2008 at 1:41 PM, Saturn <mrnobody1...@gmail.com> wrote:
> The Feed Validator clearly isn't updated with the new Daylight Saving > dates, since it comes up with "implausible date" for every feed I > test... Time to update the date of the server guys ;)
Can you give an example feed?
Here's an example of a problem that is correctly reported:
How does the validator handle time zones? I consistently get the
"Implausible date:" error on this a feed, when the date is absolutely
correct. (Feed URL: http://www.cherrytreepublications.co.uk/rss) The
feed otherwise validates, but that date issue is a frustrating niggle!
Thanks for any help with this.
David wrote: > How does the validator handle time zones? I consistently get the > "Implausible date:" error on this a feed, when the date is absolutely > correct. (Feed URL: http://www.cherrytreepublications.co.uk/rss) The > feed otherwise validates, but that date issue is a frustrating niggle! > Thanks for any help with this.
Based on your DNS name, I take it that you are in the UK, and therefore on BST at the moment? BST is +0100, but what I see in that feed is dates that end with +0000.
Internally, the feed validator converts both the current time and the dates it finds in the feeds to GMT, and compares them. In your feed, the pubDate and lastBuildDate are consistently one hour in the future. Something that seems somewhat implausible.
On May 7, 12:26 pm, Sam Ruby <ru...@intertwingly.net> wrote:
> .... In your feed,
> the pubDate and lastBuildDate are consistently one hour in the future.
> Something that seems somewhat implausible.
But somehow, quite cool! :) Thanks for the explanation -- most
helpful! I don't suppose there is a way of automagically checking for
"-Saving Time" variations? Or maybe I had better search through the
postings.
