After upgrade to Yokohama issue with "MIME type mismatch for file:" errors in our instances, while creating attachment record through REST using "multipart/form-data". - Support and Troubleshooting

After upgrade to Yokohama issue with "MIME type mismatch for file:" errors in our instances, while creating attachment record through REST using "multipart/form-data". .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } Issue:

After upgrade to Yokohama issue with "MIME type mismatch for file:" errors in our instances, while creating attachment record through REST using "multipart/form-data".

Release:

Fixed in Zurich release.

Resolution: For this to work in your instance post Xanadu, the mime type property should be set to false glide.security.file.mime_type.validation

This "glide.security.mime.type.detection.allow_file_name_as_hint" property controls the actual type of uploaded attachment. If "glide.security.mime.type.detection.allow_file_name_as_hint" is set to true, file mime type detection will consider file name extension.

Due to the security issue it may cause and to prevent putting new instances at risk, the Product Dev team made a change to set "glide.security.mime.type.detection.allow_file_name_as_hint" to the value "false" by default from the Xanadu release.

Please refer to the documentation link for more details: As per the product documentation:

https://www.servicenow.com/docs/bundle/yokohama-api-reference/page/integrate/outbound-rest/task/t_DefineAnHTTPHeader.html

The multi-part content type is not supported in the REST Message Apis. Customers are advised to use REST STEP from flow designer.

As it was never intended to support multipart content.

Please refer to the Problem record for more details:

PRB1847747