Filter added to non-FHIR APIs

[danielelkington]

Describe the bug
We are using Spark to add FHIR endpoints to an existing application - our existing APIs have prefix /api while the new FHIR apis will have the prefix /fhir. However calling services.AddFhir as recommended registers the UnsupportedMediaTypeFilter. As a result many of our existing non-FHIR APIs that receive Content-Type headers such as multipart/form-data suddenly fail.

Workaround is to rename all such APIs to include the phrase "binary" in their route.

To Reproduce

1. Create a non-FHIR API that accepts multipart/form-data
2. Call services.AddFhir to allow for FHIR APIs in the same Web API project
3. Call the non-FHIR API with header Content-Type = multipart/form-data

Expected behavior
Adding FHIR to a project should not affect non-FHIR APIs

Spark version

• Version: 2.3.1