Re: [Acme] time in the specification

Richard Barnes wrote: What's the use case for this? Diagnosing clock issues? Sometimes the spec lists an expires time and says what to do if time is before/after. It's hard to tell if the time in a response is supposed to be in the future when it's in fact in the past.

Re: [Acme] time in the specification

What's the use case for this? Diagnosing clock issues? On Feb 20, 2017 12:14 AM, "Josh Soref" wrote: There are lines of the form: > "expires": "2016-01-01T00:00:00Z", It would be helpful if the specification defined what time "now" was either generally for things in the

[Acme] time in the specification

There are lines of the form: > "expires": "2016-01-01T00:00:00Z", It would be helpful if the specification defined what time "now" was either generally for things in the specification, or for each blob. It's probably possible to include a "Date" field in most response headers (I'm less certain