Timestamps should be in milliseconds

pull/977/head
Travis Ralston 6 years ago
parent cad1db2a14
commit bdccfca726

@ -66,7 +66,7 @@ properties:
expired_ts: expired_ts:
type: integer type: integer
format: int64 format: int64
description: POSIX timestamp for when this key expired. description: POSIX timestamp in milliseconds for when this key expired.
required: true required: true
example: 922834800000 example: 922834800000
key: key:

@ -51,8 +51,8 @@ paths:
type: integer type: integer
format: int64 format: int64
description: |- description: |-
A millisecond POSIX timestamp indicating when the returned certificates A millisecond POSIX timestamp in milliseconds indicating when the returned
will need to be valid until to be useful to the requesting server. certificates will need to be valid until to be useful to the requesting server.
If not supplied, the current time as determined by the notary server is used. If not supplied, the current time as determined by the notary server is used.
required: false required: false
@ -111,9 +111,9 @@ paths:
type: integer type: integer
format: int64 format: int64
description: |- description: |-
A millisecond POSIX timestamp indicating when the returned A millisecond POSIX timestamp in milliseconds indicating when
certificates will need to be valid until to be useful to the the returned certificates will need to be valid until to be
requesting server. useful to the requesting server.
If not supplied, the current time as determined by the notary If not supplied, the current time as determined by the notary
server is used. server is used.

Loading…
Cancel
Save