I got the 403 error when upload the large file (more than 40MB) as the image below. Could you please help to share why the error here even the limit file fize is 0.
Hi @Loc Dinh Xuan change in this action earlier this was zero assigned the configure value try this
Hi @Muhammad Shehroz Ali I tried to use your suggestion but still error. I attached my OML file below.
Have you change the value from configs screen?
I haven't changed the value from config screen Ali. The maxfilesize in debug mode is still 0. But the 403 error is appeared when upload the 30MB file
Try to change the value from config screen and add maximum file size there you need.
I tried to upload 40mb file and its uploaded successfully as you can see belowand configs
Hello Loc, Let me have a look at what might cause a 403 and get back to you.
I can confirm the previous suggestion will not help you. I think Muhammad is just trying to helpful.
Kind regards,
Stuart
Besides a problem with policies in the S3 bucket (but I don't know if there is a policy related to the size of the files), it may be possible for "middle" software to also return 403 if they are configured to deny requests that are bigger than a certain size.
Hello Loc, I can't seem to cause the same issue.
A 403 in OutSystems is normally an authorization error, that is, the use does not have the right roles to execute the action, however, this shouldn't happen with the call to upload a file chunk.
Do you have the latest version of the component?
Hey Stuart!
I don't think the error is coming from OutSystems.
As they can upload files, just not big ones, I would say the error is coming from aws itself (some police related to the size of the file), or the request is not even getting there, with something else in the middle blocking the request (because of the request size)
Cheers.
Hi Eduardo,
Thanks for your help. I do think it is quite unlikely to trip AWS limits on size as the component chunks uploads, so does not attempt to upload 40MB in one go. Also 40MB is quite a small file to trip AWS limits.
However, you may have a point with respect to AWS as the example shows Loc trying to upload a .exe file, Service Studio in fact. Maybe AWS is being triggered there.
Loc could you try uploading a file that would be a realistic example, that is a large PDF or large MSWord file?
Please be considerate in terms of support; if it is not a real world example, remember we do not get paid to support forge components, so it is in our own free time this is done.
Loc, could you also post what you see in the server logs, both general and error logs.
Hi,
I think it's possible to limit the size of files being uploaded to S3 if you use pre-signed URLs. In this case, even if the component sends the file in chunks, it would still send the information about the total size, right?
But you are right that probably the extension (exe) is more likely to be the culprit. I never noticed it.
Cheers!
Hi Eduardo, Thanks, yes I only just noticed it with my last comment too.
This component does not use S3 either it just stores files in the database, so S3 is not likely to cause any issues; still I appreciate you thinking of that angle.
Why was I think about S3??? I may have confused with another post.
But if the component only stores things in the database, why is he receiving a 403?
I mean, OuSystems would trigger an exception, not a 403, right? In case of a permissions issue? And a permission issue at the OutSystems level would trigger to any file, not a specific one...
I am intrigued... :D
Is the component sending things directly to the database, from client?
The error seems to happen when the request is made from the browser, not as a response from OutSystems...?EDIT:Actually looking to the error messages, it seems the action being called was not even executed.
So, I would say it's not a component problem, if it works with smaller/other extensions files, nor an OutSystems issue, as any issue inside the action or with missing roles would trigger an exception, not a 403.
I am pretty sure there is something between the browser and the server (like a firewall, a load balancer or something else) that has a configuration and is refusing the request with a 403.
The why is trickier for me, as I don't know how the component sends the file to the server. But it got me curious, so I will take a look at the component when I have more time :)Cheers!