从群组迁移API的插入方法获取以下503响应(https://developers.google.com/google-apps/groups-migration/v1/reference/archive/insert)。
我只是尝试使用示例有效负载来处理尖峰 - 但是如果我操作POST,我可以得到401或404错误;无法创建400错误。是否有其他人成功使用此API?该服务是否存在暂时的服务问题?
谢谢! 克里斯
REQUEST:
POST https://www.googleapis.com/upload/groups/v1/groups/testmaspa@googlegroups.com/archive? uploadType=media HTTP/1.1
Content-Type: message/rfc822
Authorization: Bearer blah...
Host: www.googleapis.com
Content-Length: 470
Expect: 100-continue
Received: by 10.143.160.15 with HTTP; Mon, 16 Jul 2007 10:12:26 -0700 (PDT)
Message-ID: NNNN@mail.samplegroup.com
Date: Mon, 16 Jul 2007 10:12:26 -0700
From: "chris@mnaspa.org"
To: "chris@mnaspa.org"
Subject: TEST SUBJECT
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Delivered-To: testmaspa@googlegroups.com
This is the body of the migrated email message. Booyah!
响应:
HTTP/1.1 503 Service Unavailable
Server: HTTP Upload Server Built on Dec 3 2012 11:16:02 (1354562162)
Content-Type: application/json
Date: Sat, 08 Dec 2012 00:36:53 GMT
Pragma: no-cache
Expires: Fri, 01 Jan 1990 00:00:00 GMT
Cache-Control: no-cache, no-store, must-revalidate
Content-Length: 177
{
"error": {
"errors": [
{
"domain": "global",
"reason": "backendError",
"message": "Backend Error"
}
],
"code": 503,
"message": "Backend Error"
}
答案 0 :(得分:2)
503是overquota,通常......最近发生了很多......可能是由于Group Settings API的一些新增功能?我们增加了配额,仍然收到500个错误。
我们有一张票,它已被确认为一个问题,正在调查中。一些稳定性已经恢复,但对我们来说仍然是一个大问题。
我们的每日配额限制请求尚未增加,但可能会每周审核这些请求。
祝你好运, 大卫
答案 1 :(得分:0)
您应该将消息ID从NNNN@mail.samplegroup.com更改为< NNNN@mail.samplegroup.com>