def get_timestamp(self):
commitment = self.path[len('/timestamp/'):]
try:
commitment = binascii.unhexlify(commitment)
except binascii.Error:
self.send_response(400)
self.send_header('Content-type', 'text/plain')
self.send_header(
'Cache-Control',
'public, max-age=31536000') # this will never not be an error!
self.end_headers()
self.wfile.write(b'commitment must be hex-encoded bytes')
return
try:
timestamp = self.calendar[commitment]
except KeyError:
self.send_response(404)
self.send_header('Content-type', 'text/plain')
# Pending?
reason = self.calendar.stamper.is_pending(commitment)
if reason:
reason = reason.encode()
# The commitment is pending, so its status will change soonish
# as blocks are found.
self.send_header('Cache-Control', 'public, max-age=60')
else:
# The commitment isn't in this calendar at all. Clients only
# get specific commitments from servers, so in the current
# implementation there's no reason why this response would ever
# change.
#
# FIXME: unfortunately, this isn't actually true, as the
# stamper may return `Not Found` for a commitment that was just
# added, as commitments aren't actually added directly to the
# pending data structure, but rather, added to the journal and
# only then added to pending. So for now, set a reasonably
# short cache control header.
#
# See https://github.com/opentimestamps/opentimestamps-server/issues/10
# for more info.
self.send_header('Cache-Control', 'public, max-age=60')
reason = b'Not found'
self.end_headers()
self.wfile.write(reason)
return
self.send_response(200)
# Since only Bitcoin attestations are currently made, once a commitment
# is timestamped by Bitcoin this response will never change.
self.send_header('Cache-Control', 'public, max-age=3600')
self.send_header('Content-type', 'application/octet-stream')
self.end_headers()
timestamp.serialize(StreamSerializationContext(self.wfile))
