javascript – Safari没有使用JS Fetch API设置CORS cookie

在使用Fetch API时(实际上,通过 fetch polyfill),我无法让Safari在服务器响应中成功应用Set-Cookie.相同的代码在FF和Chrome中正常工作(我使用native和polyfill fetch进行了测试).

>请求跨域;
>是的,我正在设置凭据：true;
>服务器确实使用Set-Cookie标头进行响应;
>后续请求是从Chrome和FF发送的,带有cookie请求标头,但Safari不会;
>请求使用HTTPS(证书是自签名的,在开发域上,但似乎是常规请求的Safari接受);和

有人知道问题可能是什么吗？

我已经阅读了文档并经历了closed bug reports的许多内容.除非我错过了什么,我想问题可能是‘default browser behaviour’处理cookie和CORS – 而不是fetch(通过polyfill源代码阅读,似乎100％无知的饼干).一些错误报告表明,格式错误的服务器响应可能会阻止cookie被保存.

我的代码看起来像这样：

function buildFetch(url,init={}) {
    let headers = Object.assign({},init.headers || {},{'Content-Type': 'application/json'});
    let params = Object.assign({},init,{ credentials: 'include',headers });

    return fetch(`${baseUrl}${url}`,params);
}

buildFetch('/remote/connect',{method: 'PUT',body: JSON.stringify({ code })})
.then(response => response.json())
.then(/* complete authentication */)

实际的授权请求如下.我正在使用cURL来获取确切的请求/响应数据,因为Safari很难复制/粘贴它.

curl 'https://mydevserver:8443/api/v1/remote/connect' \
-v \
-XPUT \
-H 'Content-Type: application/json' \
-H 'Referer: http://localhost:3002/' \
-H 'Origin: http://localhost:3002' \
-H 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/602.4.8 (KHTML,like Gecko) Version/10.0.3 Safari/602.4.8' \
--data-binary '{"token":"value"}'


*   Trying 127.0.0.1...
* Connected to mydevserver (127.0.0.1) port 8443 (#0)
* TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
* Server certificate: mydevserver
> PUT /api/v1/remote/connect HTTP/1.1
> Host: mydevserver:8443
> Accept: */*
> Content-Type: application/json
> Referer: http://localhost:3002/
> Origin: http://localhost:3002
> User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/602.4.8 (KHTML,like Gecko) Version/10.0.3 Safari/602.4.8
> Content-Length: 15
> 
* upload completely sent off: 15 out of 15 bytes
< HTTP/1.1 200 OK
< Access-Control-Allow-Origin: http://localhost:3002
< Access-Control-Allow-Credentials: true
< Access-Control-Allow-Headers: Origin,X-Requested-With,Content-Type,Accept,Api-Key,Device-Key
< Access-Control-Allow-Methods: GET,POST,PUT,DELETE,OPTIONS
< Access-Control-Expose-Headers: Date
< Content-Type: application/json; charset=utf-8
< Content-Length: 37
< Set-Cookie: express:sess=[SESSIONKEY]=; path=/; expires=Fri,17 Feb 2017 15:30:01 GMT; secure; httponly
< Set-Cookie: express:sess.sig=[SIGNATURE]; path=/; expires=Fri,17 Feb 2017 15:30:01 GMT; secure; httponly
< Date: Fri,17 Feb 2017 14:30:01 GMT
< Connection: keep-alive
< 
* Connection #0 to host mydevserver left intact
{"some":"normal","response":"payload"}