I did this to myself. By trying to "accept" wrong mime types I'm also affecting the reverse extension to mime type resolver and the other way around affecting AMI when dealing with good/valid mime types coming from another Archipelago. It is not a breaker but hinders Archipelago to Archipelago Migrations badly when dealing with 3D Models where extensions need to match 1:1 (textures defined inside a Material).
DiegoPino
commented
1 year ago
What? see https://github.com/esmero/ami/issues/173
I did this to myself. By trying to "accept" wrong mime types I'm also affecting the reverse extension to mime type resolver and the other way around affecting AMI when dealing with good/valid mime types coming from another Archipelago. It is not a breaker but hinders Archipelago to Archipelago Migrations badly when dealing with 3D Models where extensions need to match 1:1 (textures defined inside a Material).
Better way is to remove https://github.com/esmero/strawberryfield/commit/8ebc80d614e0aec84f44a519fe2e7172a535e3a0#diff-ad7caa9a352ee0e51b105c7662c7bf27b08608238cd7541eb27c61e36b117f5eR301-R306 and deal with the exceptions in AMI itself (Also I think I am doing it already ... double gosh)