We are trying to set up a HTTPS Post task. It relied upon a new feature being brought in during the previous patch, which is done, so thankyou but now we have a new issue.
We needed the content-type header to be "multipart/form-data" and not be changed to match the file type. This is now done but the website is reporting that the file is too large.
According to the support of that website, its because there has been no boundary set in our HTTPS POST request. They also state the boundary is something set by the application sending the POST, so they can't advise on what it should be.
In chat you recommended to add ";boundary=xxxxx" to our content-type header. That didn't work. The file being sent is a zip, but using "multipart/form-data" for the content-type header, what should the boundary be?