Hi Stephane,
Thanks for the tip. Even while it have bad accuracy for such users (if any)
it may be created a separate quick endpoint with empty payload, or just CGI
script.
Anyway this is expensive to do date formatting for each request and data
transmission which may be really slow for radio mesh
On the other hand, there is htpdate which is handy for
some embedded or firewalled systems.
They would loose the ability to set their time.
http://www.vervest.org/htp/
___
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/
In RFC 2616 section 14.18 said that sever MUST send Date header
https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.18
But in fact the header is often ignored and makes sense only for caching by age
`Cache-Control: max-age=21600` when server clock is wrong. But BusyBox have
support of
