当文件大小大于可恢复上载块大小时,文档列表API文件上载失败

时间:2012-04-27 12:32:33

标签: android google-docs-api google-drive-api

我正在尝试使用文档列表API获取Android应用与Google文档/云端硬盘进行互动:https://developers.google.com/google-apps/documents-list

我使用GData可恢复上传协议上传文件时遇到了一些麻烦,即: https://developers.google.com/google-apps/documents-list#uploading_a_new_document_or_file_with_both_metadata_and_content

我使用的是512KiB块大小。小于块大小的文件成功上载,但大于块大小的文件将在第一个块完成之前失败。即使我将块大小增加到1MiB或2MiB也是如此。块大小为512KiB时,768KiB文件将失败,但块大小为1MiB时会成功。

大于块大小的文件确实超过了第一步,即将XML发布到“可恢复的创建媒体”链接。然后我看到在用于发送块的HttpContent实现的writeTo()方法中抛出了SSLException。此异常发生在 FIRST 块的中间,例如:

javax.net.ssl.SSLException: Write error: ssl=0x2a6318: I/O error during system call, Broken pipe
    at org.apache.harmony.xnet.provider.jsse.NativeCrypto.SSL_write(Native Method)
    at org.apache.harmony.xnet.provider.jsse.OpenSSLSocketImpl$SSLOutputStream.write(OpenSSLSocketImpl.java:713)
    at libcore.net.http.FixedLengthOutputStream.write(FixedLengthOutputStream.java:41)
    at com.google.api.client.http.AbstractInputStreamContent.writeTo(AbstractInputStreamContent.java:89)

请注意,要查看上述内容,我必须在writeTo()方法中实际捕获IOExceptions(在记录它们之后重新抛出它们)。否则,由于内容被突然切断,我只会看到一般的“400 Bad Request”响应。

我尝试了一些不同的测试设备,例如Galaxy Nexus(VZW / CDMA,4.0.2,股票),Droid4(Moto 2.3.6,股票)DroidX(股票)。

请求上传第一个块的标题:

Accept-Encoding: gzip
Authorization: GoogleLogin auth=XXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Content-Length: 524288
Content-Range: 0-524287/1635085
Content-Type: image/png
GData-Version: 3.0
User-Agent: XXXXXXXXXXXXXX

感谢您的任何建议。

UPDATE :添加代码段,这是PUT下一个块的位。

private boolean putNext() 
throws CancelException, DirectoryException {
    try {
        ByteArrayContent content = new ByteArrayContent(mediaType, buffer, 0, bufferLength);

        HttpRequest request = conn.getHttpRequestFactory().buildPutRequest(new GenericUrl(nextLocation), content);

        HttpHeaders requestHeaders = request.getHeaders();
        requestHeaders.setContentLength(String.valueOf(bufferLength));
        requestHeaders.setContentType(mediaType);

        if (sent != 0 || bufferLength != size) {
            // Only set content range when file will span multiple chunks.
            requestHeaders.setContentRange(sent + "-" + (sent + bufferLength - 1) + "/" + size);
        }

        HttpResponse response = request.execute();

        sent += bufferLength;
        bufferLength = 0;

        HttpHeaders responseHeaders = response.getHeaders();

        int statusCode = response.getStatusCode();
        if (statusCode == GoogleDriveConnection.RESPONSE_308_RESUME_INCOMPLETE) {
            nextLocation = responseHeaders.getLocation();
            return false;
        } else if (statusCode >= 200 && statusCode < 400) {
            Document responseDom = DomUtil.load(response.getContent());
            return true;
        } else {
            Log.w(LOG_TAG, "Google Drive upload error: Invalid response code to upload request: " + statusCode);
            throw DirectoryException.networkErrorHost(null, catalog.getHostName());
        }
    } catch (IOException ex) {
        Log.w(LOG_TAG, "Google Drive write error.", ex);
        throw DirectoryException.networkErrorHost(ex, catalog.getHostName());
    } catch (SAXException ex) {
        throw DirectoryException.networkErrorHost(ex, catalog.getHostName());
    }
}

另一个可能重要的注意事项:SSLException失败是由Content-Range标头的存在触发的。如果省略它,第一块大于块大小的文件就会成功上传,没有例外。服务器返回201 Created,并使用截断的512KiB大小创建文件。

再次感谢!

更新2

我现在有一个纯Java应用程序可用于演示此问题。这被打包为包含库的Eclipse项目,但是在其他地方使用它应该是微不足道的。 http://android.nextapp.com/test/DriveUpload.zip

需要使用身份验证令牌来测试它。它需要运行三个命令行参数:

[filename] [content / type] [AuthToken]

(我目前正在从真实应用程序的调试输出中剪切/粘贴authtokens)

这是此应用程序的修剪输出:

TOKEN=********
FILE=/tmp/1199Panigale.jpg
Headers: POST Request
-- User-Agent: DriveUpload
-- GData-Version: 3.0
-- Authorization: GoogleLogin auth=********
-- X-Upload-Content-Type: image/png
-- X-Upload-Content-Length: 1635085
[POST Request] --------------------------------------------------------
<entry xmlns="http://www.w3.org/2005/Atom">
<title>1199Panigale.jpg</title>
</entry>
Executing post request: https://docs.google.com/feeds/upload/create-session/default/private/full/folder%3Aroot/contents?convert=false
Post complete, response=200
Headers: POST Response
-- Server: HTTP Upload Server Built on Apr 23 2012 11:11:29 (1335204689)
-- Location: https://docs.google.com/feeds/upload/create-session/default/private/full/folder%3Aroot/contents?convert=false&upload_id=********2
-- Date: Sat, 28 Apr 2012 04:51:47 GMT
-- Pragma: no-cache
-- Expires: Fri, 01 Jan 1990 00:00:00 GMT
-- Cache-Control: no-cache, no-store, must-revalidate
-- Content-Length: 0
-- Content-Type: text/html
Preparing PUT request #0
Headers: Put Request
-- User-Agent: DriveUpload
-- GData-Version: 3.0
-- Authorization: GoogleLogin auth=********
-- Content-Type: image/png
-- Content-Range: 0-524287/1635085
[writeTo]
[getCotent]
Read: 4096, total: 4096
Read: 4096, total: 8192
Read: 4096, total: 12288
Read: 4096, total: 16384

[---skip a few---]

Read: 4096, total: 270336
Read: 4096, total: 274432
Read: 4096, total: 278528
Read: 4096, total: 282624
Read: 4096, total: 286720
Read: 4096, total: 290816
Apr 27, 2012 9:49:02 PM org.apache.http.impl.client.DefaultRequestDirector tryExecute
INFO: I/O exception (java.net.SocketException) caught when processing request: Broken pipe
Apr 27, 2012 9:49:02 PM org.apache.http.impl.client.DefaultRequestDirector tryExecute
INFO: Retrying request
[writeTo]
[getCotent]
Read: 4096, total: 4096
Read: 4096, total: 8192
Read: 4096, total: 12288
Read: 4096, total: 16384
Read: 4096, total: 20480

[---skip a few---]

Read: 4096, total: 274432
Read: 4096, total: 278528
Read: 4096, total: 282624
Read: 4096, total: 286720
Read: 4096, total: 290816
Apr 27, 2012 9:49:02 PM org.apache.http.impl.client.DefaultRequestDirector tryExecute
INFO: I/O exception (java.net.SocketException) caught when processing request: Broken pipe
Apr 27, 2012 9:49:02 PM org.apache.http.impl.client.DefaultRequestDirector tryExecute
INFO: Retrying request
[writeTo]
[getCotent]
Read: 4096, total: 4096
Read: 4096, total: 8192
Read: 4096, total: 12288
Read: 4096, total: 16384
Read: 4096, total: 20480

[---skip a few---]

Read: 4096, total: 278528
Read: 4096, total: 282624
Read: 4096, total: 286720
Read: 4096, total: 290816
Read: 4096, total: 294912
Apr 27, 2012 9:49:02 PM org.apache.http.impl.client.DefaultRequestDirector tryExecute
INFO: I/O exception (java.net.SocketException) caught when processing request: Broken pipe
Apr 27, 2012 9:49:02 PM org.apache.http.impl.client.DefaultRequestDirector tryExecute
INFO: Retrying request
[writeTo]
[getCotent]
Read: 4096, total: 4096
Read: 4096, total: 8192
Read: 4096, total: 12288
Read: 4096, total: 16384
Read: 4096, total: 20480

[---skip a few---]

Read: 4096, total: 278528
Read: 4096, total: 282624
Read: 4096, total: 286720
java.net.SocketException: Broken pipe
    at java.net.SocketOutputStream.socketWrite0(Native Method)
    at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109)
    at java.net.SocketOutputStream.write(SocketOutputStream.java:153)
    at sun.security.ssl.OutputRecord.writeBuffer(OutputRecord.java:314)
    at sun.security.ssl.OutputRecord.write(OutputRecord.java:303)
    at sun.security.ssl.SSLSocketImpl.writeRecordInternal(SSLSocketImpl.java:768)
    at sun.security.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:756)
    at sun.security.ssl.AppOutputStream.write(AppOutputStream.java:108)
    at org.apache.http.impl.io.AbstractSessionOutputBuffer.write(AbstractSessionOutputBuffer.java:153)
    at org.apache.http.impl.io.ContentLengthOutputStream.write(ContentLengthOutputStream.java:114)
    at driveupload.UploadStream$1.writeTo(UploadStream.java:149)
    at org.apache.http.entity.HttpEntityWrapper.writeTo(HttpEntityWrapper.java:96)
    at org.apache.http.impl.client.EntityEnclosingRequestWrapper$EntityWrapper.writeTo(EntityEnclosingRequestWrapper.java:108)
    at org.apache.http.impl.entity.EntitySerializer.serialize(EntitySerializer.java:120)
    at org.apache.http.impl.AbstractHttpClientConnection.sendRequestEntity(AbstractHttpClientConnection.java:264)
    at org.apache.http.impl.conn.AbstractClientConnAdapter.sendRequestEntity(AbstractClientConnAdapter.java:224)
    at org.apache.http.protocol.HttpRequestExecutor.doSendRequest(HttpRequestExecutor.java:255)
    at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:123)
    at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:647)
    at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:464)
    at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820)
    at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:754)
    at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:732)
    at driveupload.DriveUpload.executeRequest(DriveUpload.java:71)
    at driveupload.UploadStream.putNext(UploadStream.java:191)
    at driveupload.UploadStream.write(UploadStream.java:225)
    at java.io.OutputStream.write(OutputStream.java:116)
    at driveupload.DriveUpload.test(DriveUpload.java:127)
    at driveupload.DriveUpload.main(DriveUpload.java:44)

1 个答案:

答案 0 :(得分:2)

问题是我没有在&#34;内容范围&#34;之前添加前缀。标题为&#34; bytes&#34;。我不知道为什么我在之前的六次中没有找到这个,我检查了标题与规范的一致性。 :)

感谢您的帮助,很抱歉打扰您这个非问题。

我确实注意到规格表明对PUT请求的响应将提供一个&#34;位置&#34;下一个上传的标题。我没有看到一个,但如果我坚持以前发布的位置,它可以正常工作。我的代码现在只是更新位置URL(如果要提供的话),如果不是,则继续使用之前发布的URL。