Actual file size is not matched with upload file size shown in UploadService about android-upload-service HOT 3 CLOSED

@devdivr yes, take a look here and the linked RFC: https://github.com/gotev/android-upload-service/wiki/4.x-Usage#http-multipartform-data-upload--rfc2388 Multipart Upload Protocol has boundary bytes to allow for data and parameters in a single request, therefore if you observe the request from a server, you'll see more bytes than a Binary upload.

from android-upload-service.

Hey @devdivr

fist of all, Upload Service measures file sizes in those ways:

• if you use file:/// it uses https://github.com/gotev/android-upload-service/blob/master/uploadservice/src/main/java/net/gotev/uploadservice/schemehandlers/FileSchemeHandler.kt#L18
• if you use a content resolver it uses https://github.com/gotev/android-upload-service/blob/master/uploadservice/src/main/java/net/gotev/uploadservice/schemehandlers/ContentResolverSchemeHandler.kt#L20

so as a first step it's important to know which of the two implementations is used in your specific case.

Then, how have you measured 327307520 size?

The multipart request you're using is tested both with this test suite and also against a real node.js express server which is in the examples. If you want to make some tests on your dev pc, you can easily replicate the setup by following this guide: https://github.com/gotev/android-upload-service/wiki/Upload-Service-Testbed or you can write a test which replicates this case.

At this stage there's nothing more I can say about your specific question without further evidence.

from android-upload-service.

BinaryUploadRequest made it. I don't know why but Multipart upload has more data in it?

from android-upload-service.