为什么在上传有效载荷之前CURL的PUT验证失败,但XHR PUT仅在之后?

Sat*_*ham 6 javascript curl file-upload xmlhttprequest

我正在使用基于令牌的身份验证的rest API,其中一些用户有权上传文件而有些用户没有.

问题是当一些没有权限上传文件的用户尝试上传时(说1GB文件),我只在上传了整个1GB后才收到错误响应.

如果我将请求从chrome开发人员工具复制为curl并通过终端发送,则会立即失败.

我使用具有上传权限的用户令牌测试了curl命令,它按预期工作.

那么,卷曲如何与XHR不同?

Curl是同步的,默认情况下不是XHR.我尝试使XHR同步,但它仍然必须在得到响应之前上传整个文件.

function upload(file, url) {
    var xhr = new XMLHttpRequest();
    xhr.upload.key = xhr.key = file.key
    xhr.upload.addEventListener("progress", updateProgress);
    xhr.addEventListener("error", transferFailed);
    xhr.addEventListener("abort", transferCanceled);
    xhr.open("PUT", url);
    xhr.setRequestHeader("Content-Type", "application/octet-stream");
    xhr.setRequestHeader("X-Auth-Token", service.token.token);


    xhr.addEventListener("readystatechange", function (e) {
      if (this.readyState === 4 && this.status >= 200 && this.status < 300) {
        transferComplete(e)
      }
      if (this.readyState === 4 && this.status === 0) {
        transferFailed(e)
      }
      if (this.status >= 400) {
        transferFailed(e)
      }

    });


    xhr.send(file);
}
Run Code Online (Sandbox Code Playgroud)

这是精确的curl命令,格式化为可读性:

curl 'https://my-website.com/54321/my-filename.jpg' 
  -X PUT   
  -H 'Pragma: no-cache' 
  -H 'Origin: https://my-website.com' 
  -H 'Accept-Encoding: gzip, deflate, sdch, br' 
  -H 'Accept-Language: en-US,en;q=0.8' 
  -H 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36' 
  -H 'Content-Type: application/octet-stream' 
  -H 'Accept: */*' 
  -H 'Cache-Control: no-cache' 
  -H 'X-Auth-Token: fsadgsdgs' 
  -H 'Referer: https://some-allowed-origin-referrer.com/' 
  -H 'Connection: keep-alive' 
  -H 'Content-Length: 86815' 
  -F "data=@/Users/satish/abc.jpg" --compressed --insecure 
Run Code Online (Sandbox Code Playgroud)

//除了令牌之外被剥离的标题

  curl 'https://my-website.com/54321/my-filename.jpg' 
    -X PUT  
    -H 'X-Auth-Token: fsadsdsdaf' 
    -F "data=@/Users/satish/abc.jpg" 
    --compressed --insecure 
Run Code Online (Sandbox Code Playgroud)

--- 更新21-02-2017 ---

为了排除任何API端点特定的行为,我编写了一个粗略的PHP脚本来测试这个观察,它仍然是真的.下面是我尝试上传到的php脚本.

<?php
/**
 * If I comment out the below lines, then curl is failing immediately.
 * But XHR doesn't
 **/

// http_response_code(400);
// return;

/* PUT data comes in on the stdin stream */
$putdata = fopen( "php://input", "r" );

/* Open a file for writing */
$file = fopen( "/Users/satish/Work/Development/htdocs/put-test/wow.jpg", "w" );

/* Read the data 1 KB at a time
   and write to the file */
while ( $data = fread( $putdata, 1024 ) ) {
    fwrite( $file, $data );
}

/* Close the streams */
fclose( $file );
fclose( $putdata );
?>
Run Code Online (Sandbox Code Playgroud)

Bri*_*xon 5

当curl具有需要身份验证的PUT请求时,它首先发送一个没有内容的"探测",以允许服务器在发送任何数据之前拒绝连接.

这似乎并没有被记录任何地方比在代码的注释等Curl_http()的lib/http.c.

(请注意,在7.53.0之前的curl版本(2017-02-22,比问题更新)中,有一个错误,即用户提供的Content?Length标题(或没有标题)而不是Content?Length: 0.)

XHR不实现此类探测,只是使用初始请求发送所有内容.