Incorrect mimeType in Search

Question

Hello,

I am using the following api:

POST https://graph.microsoft.com/v1.0/search/query

{
    "requests": [
        {
            "entityTypes": [
                "driveItem"
            ],
            "query": {
                "queryString": "filename:fir.txt AND path:\"https://tenant-my.sharepoint.com/sites/xxx/Documents/folder\""
            },
			fields: [
                  'mimeType',
                  'id',
                  'parentReference',
                  'createdBy',
                  'name',
                  'createdDateTime',
                  'lastModifiedDateTime',
                ],
 }    

 ] 
} 

And I receive the following result in mimeType:

For file:

application/vnd.openxmlformats-officedocument.wordprocessingml.document\n\nDocument

For folder:

Folder

The result is confusing. Is it intended to be so?

Answer 1

Hi @Olga Andreeva,

Thank you for your reply. I checked the relevant information and got the following results:

The additional string "\n\nDocument" in the mimeType property of the search result indicates that the file is a Word document.

This is because the mimeType for Word documents is "application/vnd.openxmlformats-officedocument.wordprocessingml.document", and the "\n\nDocument" string is added to indicate that it is a document file.

This behavior is expected and is not a cause for concern. But you may need to manually remove this value when using it.

Please accept my sincerely apologize for any in convenience this may cause. Thank you for your kind understanding.

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 2

Yes. The MIME type (which is what we generally refer to as the content type) tells the caller what format the data is being returned as. For an Office document it is returning the content type associated with Office documents. There is no such thing for folder so it can return whatever it wants.

If you want to ensure it returns only types you support then use the Accept HTTP header and specify the format(s) you want. In general the server will attempt to return the format you requested. If it cannot find a match then most servers tend to just fail the call but that is up to the web server.

Answer 3

Hello @Michael Taylor and @Ling Zhou_MSFT ,

Thank you for the attention to the question.

Unfortunately, I cannot find it suitable for my case. The Accept header is a general feature of the HTTP server.I am asking about the particular Microsoft Graph API case - search endpoint:

POST https://graph.microsoft.com/v1.0/search/query

{
    "requests": [
        {
            "entityTypes": [
                "driveItem"
            ],
            "query": {
                "queryString": "filename:fir.txt AND path:\"https://tenant-my.sharepoint.com/sites/xxx/Documents/folder\""
            },
			fields: [
                  'mimeType',
                  'id',
                  'parentReference',
                  'createdBy',
                  'name',
                  'createdDateTime',
                  'lastModifiedDateTime',
                ],
 }    

 ] 
} 

And after I receive the result of this query in the response body (not response content-type header) I see that for the documents there is the mimeType:

application/vnd.openxmlformats-officedocument.wordprocessingml.document\n\nDocument

As you might see additional string is added: "\n\nDocument".

For folders there is

Folder

Because of it I need to filter out the values "\n\nDocument" and "Folder" in my app to use mimeTypes efficiently.

I do not see such problem in API like:

/groups/{group-id}/drive/root/search(q='{search-text}')