Google drive api 驱动API v2&;v3(1.16)文件监视请求在使用批处理请求时被拒绝
当我尝试在批处理请求中发出文件监视请求时,收到403个watchDenied错误。正常发送就可以了。我想批量处理文件监视请求是允许的 附加信息:如果我设置了一个不正确的地址,我会得到通常不允许的webhook地址错误,如果我设置了一个虚拟文件ID,我会得到一个404,所以我不会觉得我的请求不正确 示例代码(使用C#客户端库): 正文: 错误示例Google drive api 驱动API v2&;v3(1.16)文件监视请求在使用批处理请求时被拒绝,google-drive-api,Google Drive Api,当我尝试在批处理请求中发出文件监视请求时,收到403个watchDenied错误。正常发送就可以了。我想批量处理文件监视请求是允许的 附加信息:如果我设置了一个不正确的地址,我会得到通常不允许的webhook地址错误,如果我设置了一个虚拟文件ID,我会得到一个404,所以我不会觉得我的请求不正确 示例代码(使用C#客户端库): 正文: 错误示例 { "error": { "errors": [ { "domain": "push", "reason": "watchD
{
"error": {
"errors": [
{
"domain": "push",
"reason": "watchDenied",
"message": "Watch request denied by backend"
}
],
"code": 403,
"message": "Watch request denied by backend"
}
}
开发人员支持团队更新了我提交给他们的票证 不幸的是,已知监视请求在很大程度上与 驱动批处理请求。我们的驾驶团队建议制作手表 请求与其他请求分开
POST: https://www.googleapis.com/batch
User-Agent: OverDRIVE google-api-dotnet-client/1.16.0.0 (gzip)
Authorization: Bearer [token]
Content-Type: multipart/mixed; boundary="8d7a0653-4d9b-4c09-b701-9794341f882d"
Host: www.googleapis.com
Content-Length: 988
Accept-Encoding: gzip, deflate
--8d7a0653-4d9b-4c09-b701-9794341f882d
Content-Type: application/http
POST https://www.googleapis.com/drive/v2/files/[fileId]/watch
Content-Type: application/json; charset=utf-8
Content-Length: 241
{"address":"[notification endpoint]","expiration":1474036096103,"id":"938bd983-b071-4e63-8535-f20d7f39e248","token":"[token being used]","type":"web_hook"}
--8d7a0653-4d9b-4c09-b701-9794341f882d
Content-Type: application/http
POST https://www.googleapis.com/drive/v2/files/[fileId]/watch
Content-Type: application/json; charset=utf-8
Content-Length: 241
{"address":"[notification endpoint]","expiration":1474036096105,"id":"79303874-5f6c-49aa-a601-93950895ac0f","token":"[token being used]","type":"web_hook"}
--8d7a0653-4d9b-4c09-b701-9794341f882d--
{
"error": {
"errors": [
{
"domain": "push",
"reason": "watchDenied",
"message": "Watch request denied by backend"
}
],
"code": 403,
"message": "Watch request denied by backend"
}
}