S3 UploadTask fails with some files about aws-sdk-android HOT 5 CLOSED

Hi, @ankpshah,

we have finally understood why uploads fail for some files such as ko.log: it's actually because of the configuration of the waf (Web Application Firewall), which considers that these files present a potential security risk.
The waf therefore blocks the upload but returns a 200 response, which explains why the upload is considered finalised in your code.

I can therefore close this issue.

Thank you.

from aws-sdk-android.

Hello thank you for creating this issue. Someone from our team will take look at this issue.

from aws-sdk-android.

I believe this may be related to the specific contents of a file being uploaded. To help narrow down the potential cause of the issue, would it be possible for you to verify the integrity of the file contents? Here are a few steps that could help us diagnose the issue further:

Manual Upload Test: Could you attempt to manually upload the file using the S3 console? This can help us determine if the issue lies with the file itself or the way the SDK is handling the upload.

File Integrity Check: Before uploading, could we perform a checksum comparison (e.g., using MD5) of the file on the client side and then again after uploading (if possible) to ensure the file has not been corrupted during the process?

SDK Configuration: Please let me know if there are any specific SDK configurations or settings that I should double-check on my end that might affect the upload process.

from aws-sdk-android.

Hello @salva116ario,

1. If the file is not private could you share that so we are able to replicate the issue.
2. What is the content type of the FAIL_CONTENT file? is it any different from CONTENT_OK file?
3. Whats the difference between contents of CONTENT_OK and FAIL_CONTENT file?

from aws-sdk-android.

Hi, @ankpshah
thank you for considering my request.

One way to reproduce my problem is, by example, to use these two files :

ko.log (... a file for which upload task fails)
ok.log (... with this file, all it's OK !)

I can uplaod ok.log from my Android mobile app to my s3 bucket using your lib (so, upload from mobile device storage to s3 bucket)
And I can uplaod ok.log from my PC (Windows) to my s3 bucket using WinSCP (so, from my PC storage to s3 bucket...)

But, with ko.log, the upload fails using both WinSCP (throws Internal Error) and from mobile app (but no error thrown).

It's tricky but it seems there is something wrong with this line in ko.log :
at java.lang.Thread.run(Thread.java:764)

Now, note that the same ko.log file can be uploaded on another bucket from a SpringBoot app.
So, if there is a problem with the content file, it seems that it happens only in some cases and then, we're currently trying to check our bucket configuration...

And, at last, i precise that if ko.log file is zipped before the upload, it works fine...

I'll keep you posted on the progress of our research as soon as possible.

from aws-sdk-android.