Support for verbatim multipart/related S/MIME uploads

The library already supports 2 variants of multipart uploads, which covers most use-cases.

I have a third use-case now and wonder if this can be already done with the library or would become a feature request.

I have to upload S/MIME multipart/related bodies which I already prepare myself and place them in the apps storage folder like this YYYYMMDDHHMMSSMS-<guid>.upload The content of this file is the multipart/related body that needs to be uploaded. It must not be base64 encoded or anything.

Does this already work when pointing the request to this local file and setting the Content-Type header to multipart/related?

[edeckers]

I decided to implement both discussed solutions (#137 and #138); #137 will probably be the first one I’ll work on.

[edeckers]

Your comment makes total sense to me, and I think it would be a nice feature to add to the library. I’m still pondering what solution to go with though.

As for your suggested workaround: every upload request is mapped to a multipart body, so this won’t work. This is what happens:

const request0 = {
  absoluteFilePath,
  method: 'POST',
  mimeType: 'multipart/related; boundary="===============smime.parts=="',
  url: 'http://192.168.0.147:8080',
};

const uploadResult = await BlobCourier.uploadBlob(request0)

ely@xps-ely ~ nc -l 8080
POST / HTTP/1.1
Content-Type: multipart/form-data; boundary=b3e08e48-cfca-4423-a141-e1386c4bd0bb
Content-Length: 1015
Host: 192.168.0.147:8080
Connection: Keep-Alive
Accept-Encoding: gzip
User-Agent: okhttp/3.14.9

--b3e08e48-cfca-4423-a141-e1386c4bd0bb
Content-Disposition: form-data; name="file"; filename="test.upload"
Content-Type: multipart/related; boundary="===============smime.parts=="
Content-Length: 765

(...)

It makes a good point for the verbatimBody or rawBody solution we talked about earlier in this thread though, because that would definitely solve your problem right now.

I’ll let you know what I decide on soon!