S3不放';不能在javascript中使用预先签名的URL
我已经用java为HTTP PUT方法生成了一个预签名的S3URL 略加修改的URL版本:S3不放';不能在javascript中使用预先签名的URL,javascript,url,amazon-web-services,amazon-s3,urlencode,Javascript,Url,Amazon Web Services,Amazon S3,Urlencode,我已经用java为HTTP PUT方法生成了一个预签名的S3URL 略加修改的URL版本: https://s3.amazonaws.com/somebucket/pre-signed-url-key-2?AWSAccessKeyId=BKIAIQ6H5Z7BG6KZ2ZUA&Expires=1425617244&Signature=GWcRM5ZIrAKnMJBsxyfm%2F9fyuBk%3D function ajaxUsingPresignedUrlGET() {
https://s3.amazonaws.com/somebucket/pre-signed-url-key-2?AWSAccessKeyId=BKIAIQ6H5Z7BG6KZ2ZUA&Expires=1425617244&Signature=GWcRM5ZIrAKnMJBsxyfm%2F9fyuBk%3D
function ajaxUsingPresignedUrlGET() {
$.ajax({
url: presignedURLGET,
type: 'GET',
success: function () {
console.log('Uploaded data successfully.');
}
}).done(function (data) {
console.log("DONE : " + data);
}).fail(function (e, r) {
console.log("FAIL");
});
}
我知道这是一个有效的预签名url,因为我可以将它与curl
一起用于上传文件
curl-v——上传文件somefile.txt”https://s3.amazonaws.com/somebucket/pre-signed-url-key-2?AWSAccessKeyId=BKIAIQ6H5Z7BG6KZ2ZUA&Expires=1425617244&Signature=GWcRM5ZIrAKnMJBsxyfm%2F9fyuBk%3D“
当我尝试使用以下Javascript将文件上载到同一URL时:
function ajaxUsingPresignedUrlPut() {
$.ajax({
url: presignedURLPUT,
type: 'PUT',
data: 'blah blah blah',
success: function () {
console.log('Uploaded data successfully.');
}
}).done(function (data) {
console.log("DONE : " + data);
}).fail(function (e, r) {
console.log("FAIL");
});
}
我得到403状态和响应文本
<?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>BKIAIQ6H5Z7BG6KZ2ZUA</AWSAccessKeyId><StringToSign>PUT
application/x-www-form-urlencoded; charset=UTF-8
1425617244
/somebucket/pre-signed-url-key-2</StringToSign><SignatureProvided>GWcRM5ZIrAKnMJAsxyfm/9fyuAk=</SignatureProvided><StringToSignBytes>50 55 54 0a 0a 61 70 70 6c 69 63 61 74 69 6f 6e 2f 78 2d 77 77 77 2d 66 6f 72 6d 2d 75 72 6c 65 6e 63 6f 64 65 64 3b 20 63 68 61 72 73 65 74 3d 55 54 46 2d 38 0a 31 34 32 35 36 31 37 32 34 34 0a 2f 6e 6b 6f 6e 64 72 61 74 5f 62 75 63 6b 65 74 2f 70 72 65 2d 73 69 67 6e 65 64 2d 75 72 6c 2d 6b 65 79 2d 32</StringToSignBytes><RequestId>3C8298CAC404C6F5</RequestId><HostId>uCkzA//CdCLi4SINifkIe0WH6GOlCJBgFlN8ghx8NnULEe+QVslsdoUsJc4AUdA8</HostId></Error>
我在S3存储桶上配置了以下CORS策略:
<?xml version="1.0" encoding="UTF-8"?>
<CORSConfiguration xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
<CORSRule>
<AllowedOrigin>*</AllowedOrigin>
<AllowedMethod>HEAD</AllowedMethod>
<AllowedMethod>GET</AllowedMethod>
<AllowedMethod>PUT</AllowedMethod>
<AllowedMethod>POST</AllowedMethod>
<AllowedMethod>DELETE</AllowedMethod>
<MaxAgeSeconds>3000</MaxAgeSeconds>
<ExposeHeader>ETag</ExposeHeader>
<ExposeHeader>Content-Length</ExposeHeader>
<ExposeHeader>Content-Type</ExposeHeader>
<ExposeHeader>Connection</ExposeHeader>
<ExposeHeader>Date</ExposeHeader>
<ExposeHeader>Server</ExposeHeader>
<ExposeHeader>x-amz-delete-marker</ExposeHeader>
<ExposeHeader>x-amz-id-2</ExposeHeader>
<ExposeHeader>x-amz-request-id</ExposeHeader>
<ExposeHeader>x-amz-version-id</ExposeHeader>
<AllowedHeader>*</AllowedHeader>
</CORSRule>
</CORSConfiguration>
我现在唯一的猜测是,查看url时,PUT url包含%2F
,查看它代表/
,这可能会导致浏览器出现问题?或者我完全离开了这里,还有一些其他的问题我遗漏了
编辑#1添加用于生成预签名URL的java代码
public S3GeneratePresignedUrlDemo(HttpMethod httpMethod) {
this.httpMethod = httpMethod;
System.out.println("HTTP METHOD : " + this.httpMethod);
}
@Override
public void goImpl() throws Exception {
GeneratePresignedUrlRequest request = new GeneratePresignedUrlRequest(bucketName, KEY);
request.setMethod(httpMethod);
request.setExpiration(createDateNHoursFromNow(24));
URL url = s3Client.generatePresignedUrl(request);
System.out.println(url);
}
private static Date createDateNHoursFromNow(int hours){
Date date = new Date();
long millis = date.getTime();
final int millisInSecond = 1000;
final int secondsInMinute = 60;
final int minutesInHour = 60;
millis += millisInSecond * secondsInMinute * minutesInHour * hours;
date.setTime(millis);
return date;
}`
添加
headers: {'Content-Type': 'text/plain;charset=UTF-8'},
到AJAX
function ajaxUsingPresignedUrlPut() {
$.ajax({
url: presignedURLPUT,
type: 'PUT',
data: 'blah blah blah',
headers: {'Content-Type': 'text/plain;charset=UTF-8'},
success: function () {
console.log('Uploaded data successfully.');
}
}).done(function (data) {
console.log("DONE : " + data);
}).fail(function (arg1, arg2) {
console.log("FAIL");
});
}
在生成URL时设置内容类型修复了该问题
GeneratePresignedUrlRequest request = new GeneratePresignedUrlRequest(bucketName, KEY);
request.setContentType("text/plain;charset=UTF-8");
//...
实际上,有一种更好的方法来设置内容类型,这似乎是这里的问题:
$.ajax({
url : s3presignedUrl,
type : "PUT",
data : file,
dataType : "text",
cache : false,
contentType : file.type,
processData : false
})
对您来说,重要的部分是contentType:file.type
其中file.type来自
onchange事件(它实际上显示此.files
,然后可以对其进行迭代…)
您可以在此处从我的php+js解决方案中获取完整的客户端文件:如果您不想像Nickolay Kondratyev建议的那样限制内容类型,您可以如下设置内容类型:
headers: {'Content-Type': ' '},
注意,有一个带有空格字符的字符串。非空、非未定义、空字符串或任何其他错误值。它是有效的
更新:这不再有效,S3现在检测mime类型并添加它我相信该方法(例如GET或PUT)用于生成预签名的URL,因此这可能解释您看到的问题。我在生成URL时指定了HTTP方法。如果我尝试使用
curl
上传一个包含使用GET
方法生成的URL的文件,我会得到一个错误,而curl
确实可以使用我使用PUT
生成的URL(Edit#1显示了我用于生成预签名URL的java代码),您已经接近了,确保签名匹配,并且没有额外的空格或引号。当它可用时,我会给你100分,因为我在这个问题上花了太多时间,这最终解决了它。我对curl也有同样的情况。其他内容类型也可以,只要签名和实际的PUT
请求相同。非常感谢!!花了这么多时间想弄明白