Closed GoogleCodeExporter closed 8 years ago
Does the issue only occur if you upload the file with the API? Does it work
correctly if you only use the UI to upload new revisions?
Original comment by ccherub...@google.com
on 13 Sep 2012 at 7:10
Hi Claudio,
The problem also occurs if I upload using the web interface, using the "Manage
Revisions" menu in Google Drive.
I guess it is a server problem, but it is not my place to say, and I'm not too
sure where to report that these days.
Andrew
Steps to reproduce in browser (Windows 7SP1 32 bit, Chrome 22.0.1229, same as
seen in Firefox earlier)
1. Upload a file from the desktop (drag and drop) to Google Drive.
2. Click on file in Google Drive -> Manage Revisions -> Upload new version.
3. Select new version via file picker dialog.
4. Click on file -> Manage Revisions. Select an old version
5. A new browser window opens, but hangs on "Loading"
(empty temp file is made in temp folder)
Original comment by andrew.f...@gmail.com
on 13 Sep 2012 at 7:22
Not sure if this is relevant:
in step 5 above, if you wait a few minutes the following error is shown:
The webpage at
https://doc-08-40-docs.googleusercontent.com/docs/securesc/qih29m8299ckccapa7u77
dl7q88ga49j/ok67oflgfhbqil1huvqjd58gsgigqd3/1347516000000/1832530920013930940/18
325309260013930940/0B_xd3spcGSObG16SVE5QkNndnc?e=download&rid=0B_xd3spcGSOba2hWM
2UvckRxeGtFZGYxRVo2Z1hldVVIMDdzPQ might be temporarily down or it may have
moved permanently to a new web address.
Error 337 (net::ERR_SPDY_PROTOCOL_ERROR): Unknown error.
Original comment by andrew.f...@gmail.com
on 13 Sep 2012 at 7:44
I can't reproduce this issue, it worked as expected when I followed your steps.
Are you still affected? Is it possible that something on your computer is
blocking the file download (e.g. firewall)?
Original comment by ccherub...@google.com
on 13 Sep 2012 at 2:46
I have just checked. I am still affected on two different PCs (XP with Firefox
15, and Win7 with Chrome 22), firewalls turned off.
We first heard about this problem from a client, so the problem is not isolated.
Original comment by andrew.f...@gmail.com
on 13 Sep 2012 at 9:58
We can repeat this bug on multiple browsers and PCs.
Our client who has the same bug is also in Australia. Perhaps there is
something with the Australian Google servers?
Original comment by andrew.f...@gmail.com
on 14 Sep 2012 at 5:18
I finally managed to reproduce a similar issue and a bug is filed internally to
investigate. I'll keep you updated
Original comment by ccherub...@google.com
on 14 Sep 2012 at 8:09
Thank you.
Original comment by andrew.f...@gmail.com
on 14 Sep 2012 at 11:06
Has there been a fix for this yet? I'm wondering because myself and many
others have a similar issue which is likely related to the same cause. Can't
download revisions at all. Starts to download but then quits with a Network
Error. Doesn't matter the browser or OS.
Original comment by schyler....@sdjcs.com
on 10 Oct 2012 at 5:15
A fix is currently going through the release/QA process and should tentatively
land into production next week or in two weeks.
Original comment by ccherub...@google.com
on 10 Oct 2012 at 5:20
Any update? Still affected
Original comment by bill.wil...@productivewaterservices.com.au
on 25 Nov 2012 at 7:46
I think the server side is fixed.
However, the browser client logic has changed. In step 5 in the original
report, nothing happens when the user clicks on the item now. However, drag and
drop works as mentioned here:
http://www.syncdocs.com/forums/topic/old-versions-of-files-cant-be-downloaded?vi
ew=all#post-7818
Original comment by andrew.f...@gmail.com
on 26 Nov 2012 at 4:22
Original comment by ccherub...@google.com
on 26 Nov 2012 at 4:32
Just wanted to clarify that I marked this as Fixed because the issue is no
longer related to the .NET library (it actually never was).
Original comment by ccherub...@google.com
on 26 Nov 2012 at 4:33
[deleted comment]
Yes, it is fixed, and it has nothing to do with the .NET library, it is
probably in the web browser client now.
Original comment by andrew.f...@gmail.com
on 26 Nov 2012 at 4:39
Original issue reported on code.google.com by
andrew.f...@gmail.com
on 13 Sep 2012 at 3:58