Strange answer oncreating attachment through the REST API

Hi,

We try to create new attachments at the client (WS 11.8.4.38), but the response from the WS server is invalid. The same operation in our testenvironment (11.8.4.46) works properly.

Request: Method: POST, RequestUri: 'xxxxxx/.../1089, Version: 1.1, Content:

Headers:
{
Accept: application/json
Accept: application/xml
Accept: text/xml
Connection: Keep-Alive
Accept-Encoding: gzip
Accept-Encoding: deflate
Content-Type: multipart/form-data; boundary=-----------------------------xxxxxxxxxxxxxxxxxx
Content-Length: 236435
}
-------------------------------xxxxxxxxxxxxxxxxxx
Content-Disposition: form-data; name=file; filename=a.jpg; filename*=utf-8''a.jpg
Content-Type: application/octet-stream
xxxxxxxxxxxx
-------------------------------xxxxxxxxxxxxxxxxxx--

And the response is this:

StatusCode: 200, ReasonPhrase: '', Version: 1.1, Content: System.Net.Http.HttpConnectionResponseContent, Headers:

{
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
x-permitted-cross-domain-policies: none
Strict-Transport-Security: max-age=7890000 [; includeSubDomains]
Vary: accept-encoding
Transfer-Encoding: chunked
Date: Fri, 12 Dec 2025 10:23:14 GMT
Keep-Alive: timeout=60
Connection: keep-alive
Content-Encoding: gzip
Content-Type: application/json; charset=UTF-8
}
_O 0ſK Q;` -c tL . Y:ڹ Rgf N_} ޓs w I z R Z ]d B 5 B n ľ ֢ \ @ C j z N 4 e-h WV iĊ*M{ߵ 5 䆟; nX:45 Ռ(^ʈ Y#k84L Lۀ`o Q
pT 2
C[ $ b A _ K\Z ( ʜ $ s ׋U 'j ԩϫOc f^ c * n
S 8 yy\y Xą ^ dF I O6 8 щ sv p Nѣ  8O h

So even though the status code is 200 (Success) and the response header says that the response should contain application/json (corresponds to the documentation), it is some binary content that cannot be processed.

Is this maybe a known bug in 11.8.4.38 and has been fixed in .46 ? Or how can we fix / find out the reason for this response?

thank you,

Tamas