Node.js 签名不匹配$cordovaFileTransfer
我正试图将一段视频上传到以前用Node.js 签名不匹配$cordovaFileTransfer,node.js,cordova,amazon-web-services,amazon-s3,cordova-plugins,Node.js,Cordova,Amazon Web Services,Amazon S3,Cordova Plugins,我正试图将一段视频上传到以前用$cordovaCapture录制的Amazon s3 捕获过程正常工作,作为响应,我得到对象: [MediaFile] 0: MediaFileend: 0 fullPath: "file:/storage/sdcard/DCIM/Camera/VID_20160919_144041.mp4" lastModified: null lastModifiedDate: 1474288843000 localURL: "c
$cordovaCapture
录制的Amazon s3
捕获过程正常工作,作为响应,我得到对象
:
[MediaFile]
0:
MediaFileend: 0
fullPath: "file:/storage/sdcard/DCIM/Camera/VID_20160919_144041.mp4"
lastModified: null
lastModifiedDate: 1474288843000
localURL: "cdvfile://localhost/persistent/DCIM/Camera/VID_20160919_144041.mp4"
name: "VID_20160919_144041.mp4"
size: 17098
start: 0
type: "video/mp4"
__proto__: utils.extend.F
length: 1
__proto__: Array[0]
然后,在上传视频之前,我向我的服务器请求如下:
nodeJS
getSignedUrl: function (filename, type, callback) {
if (filename) {
AWS.config.update({
accessKeyId: 'my_access_key',
secretAccessKey: 'my_secret_access_key',
region: 'my_region'
});
var s3 = new AWS.S3();
s3.getSignedUrl('putObject', {Bucket: 'my_bucket', Key: 'uploads/' + filename, ContentType: type}, function (err, url) {
if (err) {
callback(err);
} else {
callback(url);
}
});
} else {
callback('Error');
}
}
这给了我下一个端点:
https://s3-my_region.amazonaws.com/my_bucket/uploads/VID_20160919_144…=video%2Fmp4&Expires=1474289746&Signature=sF67ukPu3oELJXzsmAXCeeEJ%2FE4%3D
在我获得指向我的上传的URL
后,这里是出现问题的地方:
有此代码:
var options = {
httpMethod: "PUT",
fileName: name,
mimeType: type,
chunkedMode: 'false',
encodedURI: 'false',
headers: {
"Content-Type": type
}
};
$cordovaFileTransfer.upload(url, videoPath, options)
.then(function (result) {
callback(result);
}, function (err) {
callback(err);
}, function (progress) {
p = progress;
});
这是我得到的错误:
http status: 403
Code: 1
description: <?xml version="1.0" encoding="UTF-8"?>
<Error>
<Code>SignatureDoesNotMatch</Code>
<Message>The request signature we calculated does not match the signature you provided. Check your key and signing method.</Message>
<AWSAccessKeyId>my_access_key</AWSAccessKeyId>
<StringToSign>
PUT
video/mp4
1474291133
/my_bucket/uploads/VID_20160919_150347.mp4
</StringToSign>
<SignatureProvided>
nwLEVBOarxi7YwyB4hJ2op4j1ms%253D
</SignatureProvided>
<StringToSignBytes>
50 55 54 0a 0a 76 69 64 65 6f 2f....
</StringToSignBytes>
<RequestId>CC29DD761826BAFF</RequestId>
<HostId>
OHTLyBaAa29X04msYXqwmvr1Mw90wnPmkxXeU7pTOb9pFwDuuRXDC3AdLNwVIoEHnoUEsceWn24=
</HostId>
</Error>
听起来问题出在标题附近,但它没有按预期工作
同样,我在我的客户机中尝试了第二个选项code
,直接遵循以下文档:
具有相同的响应错误
这里我还遇到了内容类型的问题。即使在文档中声明如下:
var headers = {
"Content-Type": 'video/mp4'
};
options.headers = headers;
它向我返回了下一个错误:
http status: 501
description: <?xml version="1.0" encoding="UTF-8"?>
<Error>
<Code>NotImplemented</Code>
<Message>
A header you provided implies functionality that is not implemented
</Message>
<Header>Transfer-Encoding</Header>
<RequestId>231F38AFFBB587C6</RequestId>
.
.
.
</Error>
作为说明,我使用了一个$http.post
,就像我的其他帖子一样
更新
在这个问题上进行了更多的研究,使用nodeJS
code,我也无法上传任何东西,所以我只是这样修改了S3
构造函数:
s3 = new AWS.S3({
signatureVersion: 'v4',
region: "us-west-2"
});
curl -v -H "Content-Type: application/octet-stream" --upload-file "/Users/my_user/Desktop/VID_20160920_233443.mp4" "https://s3-us-west-2.amazonaws.com/my_bucket/uploads/VID_20160920_233443.mp4?Content-Type=video%2Fmp4&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJV3UP7LBEKPYMLGA%2F20160921%2Fus-west-2%2Fs3%2Faws4_request&X-Amz-Date=20160921T103723Z&X-Amz-Expires=600&X-Amz-Signature=8463625a45237452280b3dc9cfd89366093f7b78f8c76598ba2240f06c7f20c9&X-Amz-SignedHeaders=host%3Bx-amz-acl&x-amz-acl=public-read"
之后,通过控制台使用curl
检查,如下所示:
s3 = new AWS.S3({
signatureVersion: 'v4',
region: "us-west-2"
});
curl -v -H "Content-Type: application/octet-stream" --upload-file "/Users/my_user/Desktop/VID_20160920_233443.mp4" "https://s3-us-west-2.amazonaws.com/my_bucket/uploads/VID_20160920_233443.mp4?Content-Type=video%2Fmp4&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJV3UP7LBEKPYMLGA%2F20160921%2Fus-west-2%2Fs3%2Faws4_request&X-Amz-Date=20160921T103723Z&X-Amz-Expires=600&X-Amz-Signature=8463625a45237452280b3dc9cfd89366093f7b78f8c76598ba2240f06c7f20c9&X-Amz-SignedHeaders=host%3Bx-amz-acl&x-amz-acl=public-read"
响应成功:
* Trying 54.231.176.22...
* Connected to s3-us-west-2.amazonaws.com (54.231.176.22) port 443 (#0)
* TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
* Server certificate: *.s3-us-west-2.amazonaws.com
* Server certificate: DigiCert Baltimore CA-2 G2
* Server certificate: Baltimore CyberTrust Root
> PUT /my_bucket/uploads/VID_20160920_233443.mp4?Content-Type=video%2Fmp4&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJV3UP7LBEKPYMLGA%2F20160921%2Fus-west-2%2Fs3%2Faws4_request&X-Amz-Date=20160921T103723Z&X-Amz-Expires=600&X-Amz-Signature=8463625a45237452280b3dc9cfd89366093f7b78f8c76598ba2240f06c7f20c9&X-Amz-SignedHeaders=host%3Bx-amz-acl&x-amz-acl=public-read HTTP/1.1
> Host: s3-us-west-2.amazonaws.com
> User-Agent: curl/7.43.0
> Accept: */*
> Content-Type: application/octet-stream
> Content-Length: 18964
> Expect: 100-continue
>
< HTTP/1.1 100 Continue
* We are completely uploaded and fine
< HTTP/1.1 200 OK
< x-amz-id-2: moDxOsEISsfqjCILaIsJtl3ncc7UeH4hNNISiJeuH46MrDrHEfVm9EKC5RRkORMilDEE5z7l8cI=
< x-amz-request-id: BC345E2AC71AC019
< Date: Wed, 21 Sep 2016 10:38:05 GMT
< x-amz-expiration: expiry-date="Fri, 23 Sep 2016 00:00:00 GMT", rule-id="Delete bad uploads after 1 day"
< ETag: "7688c487b1ea40c849fdb070cf736b28"
< Content-Length: 0
< Server: AmazonS3
<
* Connection #0 to host s3-us-west-2.amazonaws.com left intact
问题仍然存在:
An error has occurred: Code = 1
upload error source cdvfile://localhost/persistent/DCIM/Camera/VID_20160921_122323.mp4
upload error target https://s3-us-west-2.amazonaws.com/my_bucket/uploads/VID_20160921_122…9e365af3f771c5d&X-Amz-SignedHeaders=host%3Bx-amz-acl&x-amz-acl=public-read
http status: 501
description: <?xml version="1.0" encoding="UTF-8"?>
<Error><Code>NotImplemented</Code><Message>A header you provided implies functionality that is not implemented</Message><Header>Transfer-Encoding</Header><RequestId>D646593FD109C0F8</RequestId><HostId>wVmGWPAAWdmSXdq5N/eO7ihqHk0GoMlXNe6k9sAyyEz55Q4k2gGgkgsgyXkh8xsxUDlmzQdAIPQ=</HostId></Error>
这里我包括我的FileUploadOptions()
:
更新2
直接尝试使用来自的$cordoviletransfer
插件时,我遇到另一个错误:
"<?xml version="1.0" encoding="UTF-8"?>
<Error><Code>AuthorizationQueryParametersError</Code><Message>Error parsing the X-Amz-Credential parameter; the Credential is mal-formed; expecting "<YOUR-AKID>/YYYYMMDD/REGION/SERVICE/aws4_request".</Message><RequestId>C863350E96804F5C</RequestId><HostId>7TmXBDlsGNvDmLFKgLePTMAg+Onf8y1ZPTEWmbdHPAyWHFIdt1+5J7U3H8Ygnf3sebMRpRNdxXA=</HostId></Error>"
更新3
为了尽可能地澄清一切,我已经部署了一个包含所有后端/前端的应用程序
再次感谢
更新4
多亏了达泽的帮助,我可以得到我的推杆的头球。在这里,我粘贴结果:
HTTP/1.1 400 Bad Request
x-amz-request-id 3F686CFD09B5C6DD
x-amz-id-2 KDrmvzhnrWfLB+Tdttg88MaPVOp2LOBAhwEqiBR0XdMpaje3lRsiM6mHfjv5ULzD7GweiT9C2T0=
Content-Type application/xml
Date Sat, 24 Sep 2016 17:00:03 GMT
Server AmazonS3
Transfer-Encoding chunked
Proxy-Connection Close
PUT /my_bucket/uploads/VID_20160924_190000.mp4?Content-Type=video%252Fmp4&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJV3UP7LBEKPYMLGA%252F20160924%252Fus-west-2%252Fs3%252Faws4_request&X-Amz-Date=20160924T170002Z&X-Amz-Expires=600&X-Amz-Signature=ca3c992290bdf51e14bab6d67e4c520b280368bdd2a0274b552dc3e975f55c9d&X-Amz-SignedHeaders=host%253Bx-amz-acl&x-amz-acl=public-read HTTP/1.1
Content-Type application/octet-stream
Content-Length 56116
User-Agent Dalvik/2.1.0 (Linux; U; Android 5.0; Aquaris E5 HD Build/LRX21M)
Host s3-us-west-2.amazonaws.com
Connection Keep-Alive
Accept-Encoding gzip
然后我意识到有两个参数错误:
Content-Type: application/xml
Transfer-Encoding: chunked
同时,我也意识到了编码。它应该是%2F
,就像%252F
这很奇怪,因为我使用参数的方式似乎是正确的:
options = {
fileKey: 'file',
fileName: name,
chunkedMode: false,
httpMethod: 'PUT',
mimeType: "application/octet-stream",
headers: {
"Content-Type": "application/octet-stream"
}
};
$cordovaFileTransfer.upload(server, filePath, options)
.then(function (result) {
console.log(result);
}, function (err) {
console.log(err);
}, function (progress) {
console.log(progress);
});
同样,感谢bvakiti,我意识到有一条错误消息,因为我正在将视频发送到https
。我正在尝试http
我想从AWS派生访问密钥时会出现一些问题
尝试使用以下方法:
function getSignatureKey(key, dateStamp, regionName, serviceName) {
var kDate= Crypto.HMAC(Crypto.SHA256, dateStamp, "AWS4" + key, { asBytes: true})
var kRegion= Crypto.HMAC(Crypto.SHA256, regionName, kDate, { asBytes: true });
var kService=Crypto.HMAC(Crypto.SHA256, serviceName, kRegion, { asBytes: true });
var kSigning= Crypto.HMAC(Crypto.SHA256, "aws4_request", kService, { asBytes: true });
return kSigning;
}
我还发现了一个旧博客,如果它有帮助的话:
上传时,如果正文/内容长度为空,可能会出现问题
看看这条线:
更新AWS bucket配置后,在创建S3对象时不要传递参数。试试下面的代码
// make managed upload
var upload = new AWS.S3.ManagedUpload({
params: metadata
});
var s3Head = new AWS.S3();
在routes/endpoints.js中进行更改。在文件传输过程中,我遇到了错误代码1的问题,并给出了html元素作为响应
问题在于SSL连接。尝试在服务器url中使用http而不是https,这样会很好。
但当涉及到身份验证时,您将在后端进行更改。cordovaFileTransfer没有问题
希望这能有所帮助。您从AWS
获取的端点与您使用$cordovfiletransfer
的方式之间似乎存在冲突
当您在服务器中获得带有s3.getSignedUrl
的端点时,只对响应URL的参数进行编码(基本URL保持非编码)
当您使用$cordoviletransfer
时,该函数会再次对参数进行编码,这就是为什么您会看到与/
匹配的%252F
有3种选择:
- 相反,在调用
$cordoviletransfer
之前,请解码参数
var host = server.split('?')[0] + '?' + decodeURIComponent(server.split('?')[1]);
- 使用中所述的
options.params
其他帮助注释中建议的选项encodeURI:false
对我不起作用
希望有帮助。阅读您传递给我的文档时,它说:您不必手动执行派生签名密钥和向请求添加身份验证信息的步骤。
使用aws sdk
。您是否尝试过使用Fiddler分析Cordova的请求?我一直在尝试使用charles
,作为拦截trafic的代理,但由于我在adb
中,所以它不起作用。我将尝试使用这个新工具,因为我不知道它。这里是Fiddler+Android的帮助链接:@DevStarlight建议您查看此链接-krilnon的评论说,添加额外的头导致了问题。关于ngCordova的双重编码问题:(尝试将encodeURI:false
添加到选项中)即使这个线程引用了服务器端的上传(这不是我的目标)。我尝试在客户端设置Content Length
,因为我有参数,但它始终给出相同的错误代码(501)。此时,您是否能够使用任何方法将任何内容上传到您的bucket?更准确地说,aws cli是的,如果我使用有效的$http.post
,并且它正确地放置在文件夹中。您能检查一下吗(如果您已经阅读了它,可能会再次检查):我无法验证您提供的签名(nwleboarxi7ywyb4hj2op4j1ms%253D)根据文件,似乎有点奇怪,关于你所说的内容的签名是为了保护我的证件和其他东西而故意修改的。实际上,我再次检查了您提供给我的AWS
post;)该解决方案是否面向在服务器端签名后直接上传?我要找的是客户端上传,方法是在服务器之前请求一个signedURL
。@DevStarlight您对此进行了检查吗?实际上这是我问题的真正解决方案,尽管第一个选项可能更有效。如果在AWS
上生成endpoint
时只想添加一些额外的参数,则建议使用第二个选项
var host = server.split('?')[0] + '?' + decodeURIComponent(server.split('?')[1]);