cfml

so <@U06TT6XF1> let's figure out this one? <https://cfml.slack.com/archives/C06TA0A9W/p1667921083984159?thread_ts=1667914889.808289&amp;cid=C06TA0A9W>

There is another developer, <@U22AV29L1>, that was primarily troubleshooting this, but he is out today. Basically we were making an API call to the Adobe Document Server API and in 5.3.8, the filecontent was coming back as binary, but the same call in 5.3.9 was coming back as an array with two rows, which is what we needed to process.

ok, I have created a ticket <https://luceeserver.atlassian.net/browse/LDEV-4264> any steps to reproduce would be great, or  screenshot, raw response capture

<@U06TT6XF1> <@U22AV29L1> Did the Adobe Document Server API return the multipart response? If yes then the 5.3.8 returns content as binary due to the bug in cfhttp handling multipart response.
<https://dev.lucee.org/t/cfhttp-handling-of-multipart-response-no-longer-working-as-expected/5842>
<https://luceeserver.atlassian.net/browse/LDEV-3545>

This bug was solved in 5.3.9.

If that's not your issue means as zac mentioned please provide some more details to replicate the issue

added usage notes <https://github.com/lucee/lucee-docs/commit/4be283441e1a5cb15cc7179411c2fc53f261865d>

<https://docs.lucee.org/reference/tags/http.html#usage-notes>

thanks to <@U01UMF483V4> for suggestion we add the usage notes section to lucee docs

<@U3K7R5W75> I think what you mentioned, `CFHTTP Handling of Multipart Response No Longer Working as Expected` is what we were seeing. It bit us because we had 5.3.9 in our lower environments but prod still had 5.3.8, which we didn't realize.  <@U22AV29L1> can you confirm? Thanks.

Yep that was it. We upgraded to 5.3.9 and everything worked great.