Mimetypes

This page provides guidance on how mimetypes are deployed.

Avoiding restarts when mimetype properties do not change

Starting in 3.8.1, the MimetypeManager includes support - which is enabled by default - for determining if a mimetype's properties are different or not when a mimetype is being updated. If the properties are not different, then no call is made to the Manage API. This avoids a restart, because if a call is made - even if the properties are not different - the Manage API will trigger a restart in MarkLogic. If logging is set to at least the info level, you'll then see the following log message (using a mimetype of "application/ditamap+xml" as an example):

The properties in the payload for mimetype application/ditamap+xml are the same as what's already set in MarkLogic, so the mimetype will not be updated

However, if the mimetype properties do differ, the mimetype will be correctly updated (thus triggering a restart in MarkLogic), and you'll see the following logging at the info level:

The properties in the payload for mimetype application/ditamap+xml differ from what's already set in MarkLogic, so the mimetype will be updated

This behavior can be disabled by setting the "mlUpdateMimetypeWhenPropertiesAreEqual" property to "true", which means mimetypes are always updated.