New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AWS iOS SDK working with minio #4039
Comments
|
|
Here the
Are you using a proxy in between Minio and your iOS App? |
@harshavardhana no, there is no proxy, so what should I put the services here if not |
@atom2ueki this is expected to appear in Host header. But what you pasted was:
So we guessed a proxy might be meddling the Host header. If not we have to dig deeper. BTW |
@krishnasrinivas yes, you're right, and now I've setup tls on s3.atom2ueki.com, and got another error
says that There were headers present in the request which were not signed |
configuration
Logs from docker
|
but |
The transfer-encoding header is removed by Go server we might have to support this, just like how they remove "Expect" header. 1334 if w.req.Method == "HEAD" || !bodyAllowedForStatus(code) {
1335 // do nothing
1336 } else if code == StatusNoContent {
1337 delHeader("Transfer-Encoding")
1338 } else if hasCL {
1339 delHeader("Transfer-Encoding")
1340 } else if w.req.ProtoAtLeast(1, 1) {
1341 // HTTP/1.1 or greater: Transfer-Encoding has been set to identity, and no
1342 // content-length has been provided. The connection must be closed after the
1343 // reply is written, and no chunking is to be done. This is the setup
1344 // recommended in the Server-Sent Events candidate recommendation 11,
1345 // section 8.
1346 if hasTE && te == "identity" {
1347 cw.chunking = false
1348 w.closeAfterReply = true |
But the above code is in It must be getting removed somewhere else. |
Yes you are right, but i remember seeing it somewhere that they remove it. It could be a potential bug too since Transfer-Encoding can have different encoding mechanisms they shouldn't remove it because the value is necessary. |
reproduces this problem without proxy |
@atom2ueki we'll fix it. |
@krishnasrinivas @harshavardhana
my configuration changed a bit, endpoint url changed from https://s3.atom2ueki.com to https://s3.atom2ueki.com/minio request header
|
Ping @atom2ueki the request header is set by you or AWS SDK. ? Looks like transfer-encoding has a wrong value is odd here? |
@harshavardhana yes, this header is getting from
if you free, you can have a try with the code I shared with you |
Will do thanks @atom2ueki |
fixes minio#4039 When x-amz-content-sha256 header is missing assume e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 as the SHA256 value for calculating canonical-request.
Keeping this open until we validate the fix merged in with the aws-ios-sdk #4064 |
@atom2ueki can you check with minio:edge
|
@krishnasrinivas @harshavardhana server side error changed to
client side error remain
|
@atom2ueki we tested your MinioTest project which seems to be working fine. do you have a sample code which we can try? |
Can you paste also the headers printed this looks like a short message. |
@harshavardhana I'm using same project I shared to you, let me ensure everything is setup correctly and test again |
@hackintoshrao - Mint should test for this. |
@atom2ueki does MinioTest repo have all the changes that you have locally? Because when we run from MinioTest it uses non-streaming signature, but the headers that you have pasted shows streaming signature. If you have any changes locally can you push it? |
@atom2ueki here are the results
We used |
@harshavardhana @krishnasrinivas I get this works! you guys awesome, thanks |
aws-amplify/aws-sdk-ios#638 here is the relevant PR with this change it works with nginx+minio on https://s3.atom2ueki.com Thanks for all the help on this @atom2ueki |
// cc @laurentgdh here since you opened #4101 |
Can this be closed then ? @atom2ueki @krishnasrinivas |
Thanks @harshavardhana ! It's working now. |
@deekoder yes, this one can closed |
File an issue on golang @harshavardhana and then close this issue. |
aws-amplify/aws-sdk-ios#638 fixed upstream. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Error messgae
SignatureDoesNotMatch
The request signature we calculated does not match the signature you provided. Check your key and signing method./images/test.jpg3L1373L137Upload failed with error: (The operation couldn’t be completed. (com.amazonaws.AWSServiceErrorDomain error 3.))
Here is how I configure
Possible Solution
refer to this issue, minio/mc#1707
maybe it caused by region issue?
Your Environment
Version used:
The text was updated successfully, but these errors were encountered: