上傳到S3時出現錯誤的XMLHttpRequest

Question

我正在使用Evaporate.js將文件上傳到S3。 在我決定啟用服務器端加密之前，我已經完成了所有工作。

根據S3文檔，您可以通過傳遞標頭來啟用它。 所以我更新了我的添加代碼，如下所示：

var promise = _e_.add({
            name: name,
            file: files[i],
            started: callback_methods.started,
            complete: callback_methods.complete,
            cancelled: callback_methods.cancelled,
            progress: callback_methods.progress,
            error: callback_methods.error,
            warn: callback_methods.warn,
            paused: callback_methods.paused,
            pausing: callback_methods.pausing,
            resumed: callback_methods.resumed,
            nameChanged: callback_methods.nameChanged,
            xAmzHeadersAtInitiate: { 'x-amz-server-side​-encryption': 'AES256'} // THIS IS THE ONLY LINE THAT CHANGED!!!
          }
          )

我收到錯誤： DOMException: Failed to execute 'setRequestHeader' on 'XMLHttpRequest': 'AWS4-HMAC-SHA256 Credential=XXXXXXXXXXXXXXX/XXXXXXX/us-east-1/s3/aws4_request, SignedHeaders=content-type;host;x-amz-date;x-amz-server-side​-encryption, Signature=XXXXXXXXXXXXXXXXXXXXX' is not a valid HTTP header field value.

Answer 1

更新：

標題字段只能是ASCII字符。 x-amz-server-side-encryption包含隱藏字符。 鍵入它而不是從某處復制粘貼它。 從您的問題復制后，轉到此網頁並粘貼標題字段名稱，您將看到我的意思。

從文檔 ：

使用預先簽名的URL上載對象時，無法強制執行是否使用SSE-S3加密對象。

您需要將標題與URL一起簽名。 只是在簽署URL后發送標題將不起作用。

var promise = _e_.add({
    name: name,
    file: files[i],
    started: callback_methods.started,
    complete: callback_methods.complete,
    cancelled: callback_methods.cancelled,
    progress: callback_methods.progress,
    error: callback_methods.error,
    warn: callback_methods.warn,
    paused: callback_methods.paused,
    pausing: callback_methods.pausing,
    resumed: callback_methods.resumed,
    nameChanged: callback_methods.nameChanged,
    signHeaders: { 'x-amz-server-side-encryption': 'AES256' }, // notice this
    xAmzHeadersAtInitiate: { 'x-amz-server-side-encryption': 'AES256'} // this should be fine now as we have the header in the signed request too but try removing this if you still get an error. S3 does not require you to re-specify the headers that were already signed.
});