add an “XML” option to the “Response format detection” setting

[swobi71]

Is there an existing request for this feature?

• I have searched the existing issues for this feature request and I know that duplicates will be closed

Is your feature request related to a problem?

Since the latest app update (Version 11.27.3) the bodies of responses with "strange" Content-Type Headers default to "Hex" view.

e.g. Content-Type: multipart/related; type="application/xop+xml"; boundary="uuid:2d96eeb9-ca40-491d-ae52-d3f41752a05e"; start="[email protected]"; start-info="application/soap+xml"

Before this update those responses were shown as "Raw"

I experimented with Fiddler and tried different "Content-Type" Headers:
“text/xml”
“application/xml”
“application/xop+xml”
“application/soap+xml”
which "helped" the "Response format detection: Auto" to display it as "XML".

Describe the solution you'd like

Could you please add the option "XML" to the "Response format detection"-Setting, so that the response body is "always" displayed as XML no matter what Content-Type?

The setting would look like

Response format detection o Auto o JSON o XML

Describe alternatives you've considered

No response

Additional context

No response

[Khuongnb]

If possible, we would like an option to completely disable the 'Response Format Detection' feature and allow us to manually choose the format for each tab. We have so many customized Content-Type that inform the HTTP client how to decrypt the response body. Because of this, it is impossible for Postman to accurately detect the response format based solely on the Content-Type, and it currently displays the response in Hex format.

For example that Postman is unable to detect the correct format, please take a look at this URL, it should display as raw text as for any HLS playlist response: http://sample.vodobox.com/planete_interdite/planete_interdite_alternate.m3u8