summaryrefslogtreecommitdiffstats
path: root/tools
diff options
context:
space:
mode:
authorasargent@chromium.org <asargent@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-02-01 18:52:18 +0000
committerasargent@chromium.org <asargent@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-02-01 18:52:18 +0000
commita241d488d2b2be5a05149aa41f7920da9049983b (patch)
tree471548e49d6f8b65ad58b3008dc5b0c24db8f18e /tools
parent987d506a369f70966f4236917cdca7cde8e68e3d (diff)
downloadchromium_src-a241d488d2b2be5a05149aa41f7920da9049983b.zip
chromium_src-a241d488d2b2be5a05149aa41f7920da9049983b.tar.gz
chromium_src-a241d488d2b2be5a05149aa41f7920da9049983b.tar.bz2
Get rid of check that caused redirects to fail extension updates.
When the extension autoupdater downloads .crx files, we rely on the UrlFetcher class to do it for us. Inside OnCrxFetchComplete I had put a sanity check that the url we finished with was the same one we started with, but of course this breaks the case of redirects and wasn't needed because the API of UrlFetcher is that there's one UrlFetcher per outstanding fetch. BUG=26177 TEST=Extension Autoupdate should keep working normally, and work with redirects such as the example mentioned in the bug. Review URL: http://codereview.chromium.org/549215 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@37718 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions