16
Views
4
Comments
[S3 PreSigned File Upload Helper] ODC Large File Upload to AWS S3: Files Above ~400MB Become 0 Bytes in Binary Data
Question
S3 PreSigned File Upload Helper
Forge asset by OutSystems Labs

Hi

I am implementing large file uploads in an OutSystems ODC Web/Mobile app using AWS S3 Pre-Signed URLs with CORS. 

When uploading a 500 MB file:

In the debugger:

  • FileName is correctly populated

  • FileContent shows BinaryData (0 bytes)

But for 350 MB files:

  • FileContent shows correct size (hundreds of MB in bytes)

So when the file exceeds ~350–400 MB, OutSystems ODC does not keep the file in memory, and it becomes empty before being sent to S3.

Can anyone please confirm whether this behavior is due to a platform limitation in OutSystems ODC, or is there any way to achieve this?



500 MB File Debugger Screenshot.png
350 MB File Debugger Screenshot.png
2021-10-09 07-57-44
Stefan Weber
 
MVP

Hi, I have no direct answer to your question as I'm not using the OutSystems Labs component myself. You may want to review my own post https://without.systems/odc-with-aws-s3-browser-to-s3 regarding browser based upload.

I havent checked my own sample on files that large because for large file uploads I'm using a multipart upload to s3. However I do not have a sample to share :-(

2024-05-02 09-49-04
Murali Manoharan V
Champion

Hi
Thanks for your reply and giving the post to follow.

But here the issue is with the upload widget because I just created a flow like this in onchange event of upload widget

It shows "Not a Null file" for 350 MB file but it shows "Null File" for 500 MB file

Regards

Murali

2021-10-09 07-57-44
Stefan Weber
 
MVP

It seems to be an issue of the widget (or ODC in general). But as said, I'm not using OS Labs component.

2024-05-02 09-49-04
Murali Manoharan V
Champion
Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.