bad_timestamp

Summary

malformed timestamp header

Help

the timestamp header must be a unix-seconds integer

Details

When this fires

The x-nanook-timestamp header was present but did not parse as an unsigned integer. The verifier expects unix-seconds as a plain decimal, no fractional part, no ISO-8601, no quotes. This is almost always a custom client formatting it wrong; nanook ctl always emits a clean integer.

What to check

• Send x-nanook-timestamp as plain unix-seconds, e.g. time.time() | int (Python) or Date.now() / 1000 | 0 (JS):

curl -H "x-nanook-timestamp: $(date +%s)" ...

• Watch for middleware wrapping the value in quotes or appending units.