Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • GET requests to LDPRv URIs must support the 'Accept-Datetime' header
  • It must follow the syntax outlined in https://tools.ietf.org/html/rfc7089#section-2.1.1The response must contain headers as outlined in ticket <LDPRm GET response>
  • When a 'Accept-Datetime' is provided:
    • Must respond with a 302 status code and an empty body
    • Response must contain 'Location' header containing the URI of the LDPRm or LDPRv that was negotiated
    • Must contain all other standard LDPRm GET response headers
  • When a datetime is provided, Fedora will respond with the past LDPRm chronologically nearest (min-past) to the given header as follows:

...

Responses to LDPRm HEAD and GET requests must include headers as outlined below. A resource is a LDPRm if it is of type http://fedora.info/definitions/fcrepo#VersionedResource

  • Add HTTP header Link: rel="timegate" to the LDPRv
  • Include 'Link: rel="timemap"' on versioned resource pointing to LDPCv
  • add 'original' link header referencing LDPRv
  • Add 'Content-Location' headerAdd 'Memento-Datetime' header

Jira
serverDuraSpace JIRA
serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
keyFCREPO-2614

...