| commit | bb14f064c852c5a0782f1964eae4f4e9d34c9263 | |
| author | asargent@chromium.org <asargent@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | |
| Thu, 14 Jun 2012 01:33:06 +0000 (14 01:33 +0000) | ||
| committer | asargent@chromium.org <asargent@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | |
| Thu, 14 Jun 2012 01:33:06 +0000 (14 01:33 +0000) | ||
| tree | 286475cc0d8e1865350ebdff6d04cf53daa15c76 | treesnapshot (tar.gz zip) |
| parent | f5c5f7146897457ee6a5097d89ad2a692286f839 | commitdiff |
Better logging in extension update code for case of invalid crx urls
It turns out that calling .spec() on an invalid url just returns the empty
string (and causes a DCHECK failure).
BUG=130881
TEST=none
Review URL: https://chromiumcodereview.appspot.com/10534148
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@142058 0039d316-1c4b-4281-b951-d872f2087c98
It turns out that calling .spec() on an invalid url just returns the empty
string (and causes a DCHECK failure).
BUG=130881
TEST=none
Review URL: https://chromiumcodereview.appspot.com/10534148
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@142058 0039d316-1c4b-4281-b951-d872f2087c98
| chrome/browser/extensions/updater/extension_downloader.cc | diffblobblamehistory |