Look into how strictly get*
properties must match GET
headers
#26
Labels
correctness
Getting it right
high priority
Work on these first
needs research
More information is required
WebDAV
Specific to the WebDAV protocol/implementation
RFC 4918 implies that the
get*
properties (i.e.,getcontentlanguage
,getcontentlength
,getcontenttype
,getetag
, andgetlastmodified
) are meant to correpond toGET
response headers. Does this mean that the properties' values must match what would be returned by aGET
request to the corresponding resource? If so,dandidav
's current behavior violates this in the following ways:dandidav
sets thegetcontenttype
of blob assets to theirencodingFormat
metadata field, yetGET
ing a blob's download URL results in a response from S3 with a Content-Type ofbinary/octet-stream
(ortext/plain
for some of the JSON metadata files).dandidav
sets thegetlastmodified
of blob assets to the assets'modified
properties, yetGET
ing a blob results in an S3 response that seems to use theblobDateModified
date as "Last-Modified". (cf. UseblobDateModified
metadata instead ofmodified
property for blob assets' "modified" timestamps #17)dandidav
sets thegetcontentlength
of Dandiset versions to the total size of all assets in the version, butGET
ing a version via the WebDAV server will result in an HTML page listing its top-level contents, which usually won't be of the same size.getcontentlength
for collections be set to? Moreover, what aboutgetcontenttype
for collections?The text was updated successfully, but these errors were encountered: