In order to perform an unsafe deletion of a corrupt resource, the user must enable the option for the delete
  request. A resource is considered corrupt if it can not be successfully retrieved from the storage due to
  a) transformation error e.g. decryption failure, or b) the object failed to decode. Normal deletion flow is
  attempted first, and if it fails with a corrupt resource error then it triggers unsafe delete.

    <glob pattern="*.xslfo"/>
    <glob pattern="*.fo"/>
  </mime-type>

  <mime-type type="application/xslt+xml">
    <alias type="text/xsl"/>
    <acronym>XSLT</acronym>
    <_comment>XSL Transformations</_comment>
    <root-XML localName="stylesheet"
              namespaceURI="http://www.w3.org/1999/XSL/Transform"/>
    <glob pattern="*.xslt"/>
  </mime-type>

  <mime-type type="application/xspf+xml">