Currently, to allow other content-types which are not application/json we need to overwrite the incoming header so it pass the hardcoded logic. It would be great if we could defined the allowed values in the endpoint configuration.
Our current use case is the microsoft webhook, which need a endpoint to accept both text/plain and application/json: https://learn.microsoft.com/en-us/graph/change-notifications-delivery-webhooks?tabs=http#create-a-subscription
Currently, to allow other content-types which are not
application/jsonwe need to overwrite the incoming header so it pass the hardcoded logic. It would be great if we could defined the allowed values in the endpoint configuration.Our current use case is the microsoft webhook, which need a endpoint to accept both
text/plainandapplication/json: https://learn.microsoft.com/en-us/graph/change-notifications-delivery-webhooks?tabs=http#create-a-subscription