Ive noticed if I repeated use the same url
most of the time it will report the time with the offsett
but if you keep doing it, you often get times returned with no offset
These are throwing my app as I am relying on having accurate times returned with the offsett.
This seems to be recreatable. Just paste in the url above and fire it off. Arond every 9th or 10th call to it will drop the offset
Still a bit of a bug. just grabbing the last.json correctly gives the time as utc. i.e 7.29am however if I add offset=1 I'd expect to get back the utc + 1 hour. i.e 8.29. what I get is 9:29
It seems to be treating an offset of 1 as an offset of 2
Probably just a very minor bug somewhere in the code but a fix would be appreciated?
If the offset is set to +1 (let's call it Berlin time), then daylight savings time is applied during part of the year (including now) to get an offset of +2 for the current time zone offset: http://www.timeanddate.com/worldclock/city.html?n=37
We've made some changes to the way offset works. Offset no longer has a direct correlation with time zones, and will output the results in whatever offset is specified. For example, an offset of "-5" will always output feeds with a timestamp that includes "-5", regardless of daylight savings time.
We introduced a new parameter called "timezone" that ensures proper time zone transformation; you'll probably want to use this parameter since it's much more accurate and automatically handles any daylight savings time issues.
Most Users Ever Online: 114
Currently Browsing this Page:
Guest Posters: 1
Administrators: Hans, lee