diff options
| author | ananta@chromium.org <ananta@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-07-14 18:57:48 +0000 |
|---|---|---|
| committer | ananta@chromium.org <ananta@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2010-07-14 18:57:48 +0000 |
| commit | f56e69453eced97f31dc23bc72ae883f9e260eee (patch) | |
| tree | c17552ac780d04082e530551658c1e463256ce7a /net | |
| parent | 74f2958aec0f8d1da9df8e2e6ff0b0da846c7e01 (diff) | |
| download | chromium_src-f56e69453eced97f31dc23bc72ae883f9e260eee.zip chromium_src-f56e69453eced97f31dc23bc72ae883f9e260eee.tar.gz chromium_src-f56e69453eced97f31dc23bc72ae883f9e260eee.tar.bz2 | |
Attempt 2 at fixing the chrome frame net tests hang on the builders. This hang occurs because of a race condition
in registering the http/https protocol factories. The net tests registers a protocol factory and the Chrome
AutomationResourceMessageFilter also registers factories. If the net tests ends up being first in the chain then
the requests are incorrectly dropped.
Fix is to register the net tests protocol factory before instantiating the AutomationResourceMessageFilter.
TBR=stoyan
Review URL: http://codereview.chromium.org/2959013
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@52366 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions