summaryrefslogtreecommitdiffstats
path: root/base/field_trial.h
diff options
context:
space:
mode:
authorhclam@chromium.org <hclam@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-09-21 21:58:58 +0000
committerhclam@chromium.org <hclam@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-09-21 21:58:58 +0000
commit384e2a552494d4ccb0b34d1bb8e84af806050c41 (patch)
tree64ac08355163ef3066c565b53d7f9f2fb0aa4da2 /base/field_trial.h
parentda0c4d3a7e0c37bfc71d2cd793f9153108c27393 (diff)
downloadchromium_src-384e2a552494d4ccb0b34d1bb8e84af806050c41.zip
chromium_src-384e2a552494d4ccb0b34d1bb8e84af806050c41.tar.gz
chromium_src-384e2a552494d4ccb0b34d1bb8e84af806050c41.tar.bz2
Allow <audio> to work in extension
BUG=22152 TEST=use <audio> extension with relative paths We used to exclude file:// for checks for valid HTTP response but since chrome extension resources use chrome-extension:// as scheme response from such scheme require valid HTTP response. This change changes the logic to limit the check for valid HTTP response only for http:// and https:// schemes. This impose a strong assumption that file://, ftp:// and new protocols need to know how to handle range requests or at least know how to fail. Review URL: http://codereview.chromium.org/216022 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@26746 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'base/field_trial.h')
0 files changed, 0 insertions, 0 deletions