Google Drive API - 错误500 - 简单的API访问 [英] Google Drive API - Error 500 - Simple API Access
问题描述
我已经使用浏览器和cURL从不同的机器(PC和Linux服务器) WGET和我甚至创建了新的Google API帐户来尝试使用不同的API密钥,但它100%的时间都失败了。
示例请求URL:
https://www.googleapis.com/drive/v2/files/0By7D4SJX3kYEaGpneE1VaUN6OG8?key=MYAPIKEY
$ c $
$ p $ {
错误:{
code:500,
message:null
}
}
响应头文件:
HTTP / 1.1 500内部服务器错误
status:500内部服务器错误
版本:HTTP / 1.1
cache-control:private,max-age = 0
content-encoding:gzip
content-length: 66
content-type:application / json; charset = UTF-8
日期:2013年4月24日星期三17:39:49 GMT
过期:2013年4月24日星期三17:39:49 GMT
服务器:GSE
x-content-type-options:nosniff
x-frame-options:SAMEORIGIN
x-xss-protection:1; mode = block
Google云端硬盘服务器上有没有人知道的技术问题?我只看到另外一个关于零反馈的问题报告。
现在已解决,对于这个问题感到抱歉。
For months I've been using the Google Drive API for simple access to fetch metadata about publicly shared document IDs. All of a sudden about a week ago (April 16) it stopped working.
I've tried repeatedly from different machines (PCs and Linux servers) with browsers and cURL and WGET, and I have even created new Google API accounts to try using different API keys, but it fails 100% of the time.
Example request URL:
https://www.googleapis.com/drive/v2/files/0By7D4SJX3kYEaGpneE1VaUN6OG8?key=MYAPIKEY
Response body:
{
"error": {
"code": 500,
"message": null
}
}
Response headers:
HTTP/1.1 500 Internal Server Error
status: 500 Internal Server Error
version: HTTP/1.1
cache-control: private, max-age=0
content-encoding: gzip
content-length: 66
content-type: application/json; charset=UTF-8
date: Wed, 24 Apr 2013 17:39:49 GMT
expires: Wed, 24 Apr 2013 17:39:49 GMT
server: GSE
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
Is there a technical problem on the Google Drive servers that no one else is aware of? I've only seen one other report of this problem with zero feedback.
This is now fixed, sorry for the issue.
这篇关于Google Drive API - 错误500 - 简单的API访问的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!