1. 27 Oct, 2011 1 commit
  2. 26 Oct, 2011 1 commit
  3. 25 Oct, 2011 2 commits
  4. 24 Oct, 2011 1 commit
  5. 18 Oct, 2011 11 commits
  6. 17 Oct, 2011 2 commits
  7. 14 Oct, 2011 1 commit
  8. 13 Oct, 2011 1 commit
  9. 12 Oct, 2011 2 commits
  10. 11 Oct, 2011 1 commit
  11. 10 Oct, 2011 1 commit
  12. 30 Sep, 2011 1 commit
  13. 25 Sep, 2011 2 commits
  14. 23 Sep, 2011 2 commits
  15. 20 Sep, 2011 3 commits
  16. 16 Sep, 2011 2 commits
  17. 12 Sep, 2011 1 commit
  18. 30 Aug, 2011 1 commit
    • Jeff Davidson's avatar
      Don't change extensions for explicitly set download locations. · c21507f0
      Jeff Davidson authored
      This regression from GB was introduced by 38f17119,
      which was intended to allow duplicate downloads of the same file, adding -<n> to
      the end of file names.  As a side effect, this also activated extension validation
      logic, which adds/changes an extension to match the Mimetype.
      
      This change keeps the unique filename logic but prevents extension changes when an
      explicit filename is set.  Thus, it is still possible for the actual download
      location to differ from the requested one, but only if the file already exists.
      
      Bug: 5196436
      Change-Id: I198dc2a819c5d839a05b72c25e0830d889a9c5a3
      c21507f0
  19. 29 Aug, 2011 1 commit
    • Doug Zongker's avatar
      fix DownloadThread's use of ETag, range headers · ce3f6100
      Doug Zongker authored
      DownloadThread was only maintaining ETag and the file size for the
      duration of one HTTP request, rather than over all the requests needed
      to fetch a file, which kind of defeats the point of having them.  Fix
      this by moving several state variables from InnerState to State, and
      initializing the total bytes and current bytes values from the
      download database.
      
      Skip actually making the HTTP request if we've already downloaded all
      the bytes of the file.  This works around bug 5217390 by making the
      second DownloadThread do nothing instead of trying to fetch past the
      end of the file.  (A real fix would eliminate the race condition that
      causes the second thread to get created in the first place.)
      
      Bug: 5217390
      Change-Id: Ib5b8f87398b4ed2cb3d7f09569e245b55a89da5a
      ce3f6100
  20. 26 Aug, 2011 1 commit
  21. 22 Aug, 2011 1 commit
  22. 13 Aug, 2011 1 commit