Task #4032: Set the HTTP Content-Type appropriately for KUBI objects - Member Nodes - DataONE Tasks

Task #4032

MNDeployment #3188: Kansas University Biodiversity Institute

Set the HTTP Content-Type appropriately for KUBI objects

Added by Chris Jones over 10 years ago. Updated about 10 years ago.

Status:

Closed

Priority:

Normal

Assignee:

CJ Grady

Target version:

Operational

Start date:

2013-10-03

Due date:

% Done:

100%

Estimated time:

0.00 h

Story Points:

Sprint:

Description

In reviewing the KUBI content, I noticed that the HTTP Content-Type header field seems to always be set to:

Content-Type: text/html; charset=utf-8

This may be the default for the web server, but when downloading objects of different MIME types, they should be typed correctly. For instance, the following EML , TIFF, and RDF documents should have Content-Type values of text/xml, image/tiff, and application/rdf+xml respectfully:

https://bidataone.nhm.ku.edu/mn/v1/object/kubi.lifemapper.sdm.layers.516.eml
https://bidataone.nhm.ku.edu/mn/v1/object/kubi.lifemapper.sdm.layers.516.tif (big file, careful clicking here!)
https://bidataone.nhm.ku.edu/mn/v1/object/kubi.lifemapper.sdm.layers.516

This will enable browsers to render content correctly, and in the case of the TIFF image, will allow the browser to hand the file off to an application that can render the TIFF image.

History

#1 Updated by Chris Jones over 10 years ago

Description updated (diff)
Assignee changed from Roger Dahl to CJ Grady

Assigning to CJ

#2 Updated by Matthew Jones over 10 years ago

We've discussed providing an ObjectFormat -> MimeType mapping file to make this easier for people. The mapping file has been developed, and could be fairly easily be used by MN implementors when setting Mime types. The mapping files are in SVN, and are details are in ticket #3310, and other related tasks are in #3309.