Since the latest update (Version 11.27.3) the “default” view of my responses with “strange” content-types (multipart/related; type=“application/xop+xml”; boundary=“uuid:aaaaaaa-bbbb-ccccc”; start=“[email protected]”; start-info=“application/soap+xml”) seems to be “Hex”.
Before the update the response bodies were shown in “Raw”.
Is there a setting/script to change the default back to “Raw” (or even better “XML”)?
(I tried both “Response format detection” settings but no luck)
Thanks!
swobi
Hey @swobi71 
Welcome to the Postman Community 
Would you be able to share a curl example of a request that you’re seeing this with or something else that will allow us to reproduce what you’re seeing 
Thanks a lot for your quick answer!
I could send you the complete (anonymized) response (headers+body).
Would this help?
UPDATE:
HTTP/1.1 200 OK
Cache-Control: private
Content-Type: multipart/related; type="application/xop+xml"; boundary="uuid:2d96eeb9-ca40-491d-ae52-d3f41752a05e"; start="<[email protected]>"; start-info="application/soap+xml"
Server:
Request-Context: appId=cid-v1:e1679370-5032-404e-a096-6943e88ecc72
Date: Thu, 09 Jan 2025 23:30:14 GMT
Content-Length: 819
--uuid:2d96eeb9-ca40-491d-ae52-d3f41752a05e
Content-Type: application/xop+xml; charset=UTF-8; type="application/soap+xml"
Content-Transfer-Encoding: binary
Content-ID: <[email protected]>
<soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope"><soap:Body>[...sensitive information...]</soap:Body></soap:Envelope>
--uuid:2d96eeb9-ca40-491d-ae52-d3f41752a05e--
Hmm, the first bytes of the response body are 0D 0A
FYI: Used Fiddlerscript to change the first “Content-Type” header to “text/xml” and the “Response format detection” kicks in as expected and formats the response in pretty XML.
I know that fixing the Content-Type is the “correct” way to solve the problem, but maybe you could change the Response format detection Setting to the following?
Response format detection o Auto o JSON o XML
Did some more “fiddling” and it seems the “multipart/related” Content-Type is responsible, because with the following Content-Type Headers it worked fine:
“text/xml”
“application/xml”
“application/xop+xml”
“application/soap+xml”
SInce I can’t change the response “Content-Type” of the API on the server myself, I will use “Fiddler” to overwrite it for now. But it would be cool if Postman added an “XML” option to the “Response format detection”.
I just created a GitHub Feature Request (add an “XML” option to the “Response format detection” setting · Issue #13401 · postmanlabs/postman-app-support · GitHub) and hope for the best 