...
- Should LDPRv's return Content-Location and Memento-Datetime headers? The later is required by https://tools.ietf.org/html/rfc7089#section-4.1.2 but may not make sense in fcrepo's usage.
LDPCv Example Response
| Code Block | ||
|---|---|---|
| ||
# GET request to LDPCv
curl http://localhost/rest/a/fcr:versions -H "Accept: application/linked-format" -v
< HTTP/1.1 200 OK
< Date: Thu, 21 Jun 2017 00:06:50 GMT
< Server: Apache
< Content-Type: application/link-format
< Allow: GET, HEAD, OPTIONS, POST, PATCH, DELETE
< Accept-Post: text/turtle,text/rdf+n3,text/n3,application/rdf+xml,application/n-triples,application/ld+json,multipart/form-data,application/sparql-update
< Accept-Patch: application/sparql-update
< Connection: close
<http://localhost/rest/a>;rel="original",
<http://localhost/rest/a/fcr:versions>
; rel="self";type="application/link-format"
; from="Tue, 20 Jun 2016 18:02:59 GMT"
; until="Wed, 09 Apr 2017 20:30:51 GMT",
<http://localhost/rest/a>
; rel="timegate",
<http://localhost/rest/a/fcr:versions/20160620180259356>
; rel="memento";datetime="Tue, 20 Jun 2016 18:02:59 GMT",
<http://localhost/rest/a/fcr:versions/version_1>
; rel="memento";datetime="Fri, 06 Jan 2017 18:50:11 GMT",
<http://localhost/rest/a/fcr:versions/20170409203051112>
; rel="memento";datetime="Wed, 09 Apr 2017 20:30:51 GMT", |
Draft Tickets
Add versioning response headers to LDPRv HEAD/GET responses
...