Alternative HTTP/HTTPS response?

Rather than redirect to " https://developers.google.com/time ", it would be useful to have the ability for time.google.com:80 to respond with the current time value with some formatting parameters.

For example, these would be useful:

% curl " https://time.google.com/current "

I have a small embedded device ( https://www.espruino.com ) that doesn’t have a real-time clock or NTP library support but it does have networking and WiFi.

Additionally, it has library support for setting the devices date from ISO 8601 time string.

On bring up, the device could contact time.google.com , get the current time, and set the devices time to that time. Would be even cooler if based on the IP address, the response could estimate the TZ information.

I do see (via curl) that the redirect response does include the “Date” header but I don’t think the Espruino library has support for extracting the header information, just the returned data.

Dan

You might be interested in Roughtime, which is "mostly accurate but secure time" over HTTPS: https://roughtime.googlesource.com/roughtime

NTP doesn't have a concept of timezone.  You might be interested as well in looking instead at DHCP, particularly the extensions by which a DHCP server can provide a client with its timezone and preferred NTP server.

Many ISPs nowadays block outbound port 123 to 'unknown' NTP servers. Supposedly to thwart NTP based DDOS amplification attacks. We did run into this problem with our devices. Ability to get time over HTTP would be very helpful.

To unsubscribe from this group and stop receiving emails from it, send an email to public-ntp-discuss+unsub...@googlegroups.com .