Content-Type is no longer optional in webhook requests

Description

GitHub issue: https://github.com/mattermost/mattermost-server/issues/14485
Customer escalation: https://community.mattermost.com/core/pl/xwtyaqa493n6zrjhe1tabxenqo

PR at pr-mattermost-server-13839 (Jira ticket at MM-22247), modified the mime check, such that we now require `Content-Type` to be set in the request header.

This change was unintentional and led to breaking changes. In particular, if no Content-Type is set, the following error is returned

For more context, see the thread on community: https://community.mattermost.com/core/pl/xwtyaqa493n6zrjhe1tabxenqo

QA Test Steps

  • Execute incoming web hooks with different types of content-type header:

  • with it

  • without it

  • With wrong header

  • With wrong parameters

  • With right header but wrong parameters

Mana

None

Assignee

Mario de Frutos

QA Assignee

Ogi Marusic

Reporter

Jason Blais

Epic Link

None

Fix versions

Mattermost Team

Platform

Sprint

None

Labels

QA Testing Areas

Integrations

GitHub Issue

None

Components

None

Severity

None
Configure