You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The location returned from s3 client file upload to cloudserver is correct if the file size is less than 5MB of form <server-name>/<bucketName>/<keyName> (In client config s3ForcePathStyle is set to true). But if the file size is greater than 5MB, then the returned location is of the form <bucketName>.<server-name>/<keyName>.
This seems to happen as s3 client defaults to partSize of 5MB, but the URL / Location returned should be consistent with files greater than 5MB.
I'm unable to reproduce the behavior reported so far but still looking into it. Is it consistent or intermittent? Does it only occur when endpoint is given or same for without endpoint? Any additional info would help the investigation.
aBurmeseDev
added
response-requested
Waiting on additional info and feedback. Will move to \"closing-soon\" in 7 days.
p2
This is a standard priority issue
and removed
needs-triage
This issue or PR still needs to be triaged.
labels
May 24, 2024
then I get correct Location: 'http://127.0.0.1:8000/tenant/5MB.pdf', response for 5MB file.
But if I upload file bigger than 10MB, ex: 15MB with above partSize 10MB option, again we have same issue Location: 'http://tenant.127.0.0.1/15MB.pdf' where the URL is of form protocol://<bucketName>.<hostName>/<keyName>
so basically when we have the file which has partSize > 1, we have this issue and it is consistent.
It occurs when the endpoint is given, if I do not provide endpoint, then we get invalid access key.
Describe the bug
The location returned from s3 client file upload to cloudserver is correct if the file size is less than 5MB of form
<server-name>/<bucketName>/<keyName>
(In client config s3ForcePathStyle is set to true). But if the file size is greater than 5MB, then the returned location is of the form<bucketName>.<server-name>/<keyName>
.This seems to happen as s3 client defaults to partSize of 5MB, but the URL / Location returned should be consistent with files greater than 5MB.
Expected Behavior
Upload result {
ETag: '"a3008a5bd4094f4849e533f9bb2c5c89"',
Location: 'http://127.0.0.1:8000/tenant/5MB.pdf',
key: '5MB.pdf',
Key: '5MB.pdf',
Bucket: 'tenant'
}
Current Behavior
Upload result {
Location: 'http://tenant.127.0.0.1/5MB.pdf',
Bucket: 'tenant',
Key: '5MB.pdf',
ETag: '"2ec6f604cd08eb2e091b58f666ff0a9f-2"'
}
Reproduction Steps
Possible Solution
No response
Additional Information/Context
No response
SDK version used
aws-sdk version: 2.1621.0
Environment details (OS name and version, etc.)
NAME="openSUSE Tumbleweed" # VERSION="20240126"
The text was updated successfully, but these errors were encountered: