DT-898 Defaulting to binary HTTP body payloads #66
Conversation
| public ConformanceMessageBody(byte[] byteArrayBody) { | ||
| this.isRawByteArray = true; | ||
| this.byteArrayBody = byteArrayBody == null ? new byte[0] : byteArrayBody; | ||
| this.stringBody = new String(this.byteArrayBody, StandardCharsets.UTF_8); |
There was a problem hiding this comment.
How does this work if the content is not valid UTF-8 (which is likely for the use-cases that need raw byte transfers)?
There was a problem hiding this comment.
In my understanding, we're not allowed to change things like indentation or newline type, but the content type of these messages must remain UTF-8 even when they use JWS/JWE -- in fact the latter elements are Base64-encoded as ASCII, which is a subset of UTF-8.
There was a problem hiding this comment.
I specifically need support for https://app.swaggerhub.com/apis/dcsaorg/DCSA_EBL_PINT/3.0.0-Beta-1#/Transfer%20additional%20document/put_v3_envelopes__envelopeReference__additional_documents__documentChecksum_, which is about transferring additional documentation.
Said documentation can be any file including but not limited to PDF and will be transferred in the application/octet-stream stream. The validation will need to assert this stream matches the expected checksum, which is why we need binary transfers. However, there is no rule stating that the content will be a valid UTF-8 byte sequence. In fact, for a PDF, a zip file, scanned images, it will very likely not be valid UTF-8.
No description provided.