Bagit setting incorrect Content-Type

[artntek]

Summary: In some browsers, clicking on the MetacatUI button to download the entire dataset results in a zipfile with the wrong extension being downloaded.

Steps to reproduce

Using Safari Version 17.6, navigate to a dataset containing data objects, and click the MetacatUI button to download the entire dataset.

Observed

The package is downloaded, but the file extension is *.rdf (e.g. resource_map_doi_10.18739_A2S756M9H.rdf).

Expected

The downloaded package should have a *.zip extension (or is it *.tgz? TBC)

Workaround

If the file extension is manually changed to *.zip, double-clicking will then explode it as expected.

Additional Information

Inspecting the response headers from metacat reveals that the Content-Type header appears incorrect, and that the HTTP response code is HTTP/1.1 500 - internal server error

$ curl --head  https://arcticdata.io/metacat/d1/mn/v2/packages/application%2Fbagit-1.0/resource_map_doi%3A10.18739%2FA2S756M9H
HTTP/1.1 500 500
Date: Wed, 07 Aug 2024 18:05:08 GMT
Server: Apache
X-Frame-Options: SAMEORIGIN
Set-Cookie: JSESSIONID=389E774EBEFBE45FF405F9FD4904D5EF; Path=/metacat; Secure
Access-Control-Allow-Origin:
Access-Control-Allow-Headers: Authorization, Content-Type, Origin, Cache-Control
Access-Control-Allow-Methods: GET, POST, PUT, OPTIONS
Access-Control-Allow-Credentials: true
Connection: close
Content-Type: text/xml