Denis Walker wrote:
Max Tulyev wrote:
Hi!
I just sent a request for creating a new object in the RIPE DB, but got such error.
But we really have June, 07 now here (GMT+2) =)
Is it a bug or a feature?
Dear Max
This is a feature. You were trying to use the date 07 June 2007 when it was only 06 June 2007. We do not allow dates to be used in the future. That would make "changed:" attributes even less meaningful than they already are.
As Max pointed out, unless dates in the RIPE db all have to be in UTC, in his time zone it was already that date as his clock is 2 hours ahead of GMT which is 3 hours ahead of UTC at the moment. As the RIPE region also covers the regions into Israel and not to forget parts of Siberia, those people are about 6-8 hours ahead of the time in Amsterdam. Or is it a standard to always use UTC timestamps? Or is it GMT+1? Greets, Jeroen