Issue metadata
Sign in to add a comment
|
Downloads not showing correctly.
Reported by
jesse.m...@gmail.com,
Mar 31 2016
|
||||||||||||||||||||||
Issue descriptionChrome Version :Version 51.0.2695.0 URLs (if applicable) :http://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Win/ Other browsers tested: Add OK or FAIL, along with the version, after other browsers where you have tested this issue: IceDragon: 44.0.0.11: OK IE: 11.0 : OK What steps will reproduce the problem? (1)Download the lastest version update. (2)You see in the download tab Win%2F384244%2Fmin_installer.exe, also this is indicated in the folder it is downloaded to. I have reproduced this on both Windows 7 and Windows 10 versions of OS. This has been happening for quite a few of the latest builds. Please advise a fix/solution. What is the expected result? The file downloads with the correct name. What happens instead? The file downloads with the incorrect name, example as stated in Step 2. Please provide any additional information below. Attach a screenshot if possible.
,
Apr 5 2016
Here is what the file looks like when it is downloaded from http://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Win/ Win%2F385148%2Fmini_installer.exe. This happens on both Windows 7 and Windows 10 OS. I do not get this when downloading from other browser as stated in my initial report of this bug. Please advise a solution.
,
Jun 21 2016
Michael, I don't know which component this should be in, but I assume it has something to do with official build configs.
,
Jun 21 2016
The problem is that Google Storage encodes the path into the filename during the download. From my perspective it's a bug, but from theirs it appears to be working as intended. Not related to any configs on the official build side of things.
,
Jun 21 2016
Yeah, these are actually archives of the main waterfall builds, nothing to do with official release builds. It sounds the same as Issue 603960. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by brajkumar@chromium.org
, Apr 1 2016