diff options
| author | rvargas@google.com <rvargas@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-06-12 17:35:50 +0000 |
|---|---|---|
| committer | rvargas@google.com <rvargas@google.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-06-12 17:35:50 +0000 |
| commit | 8bf26f49ab4b5fd24fe788e4d64c8294280a118d (patch) | |
| tree | 801038a21ca17d04400cbafef4b9b50314d400a9 /chrome/chrome.gyp | |
| parent | 906a74512ed2bddab37ccab2730a17244b799d5b (diff) | |
| download | chromium_src-8bf26f49ab4b5fd24fe788e4d64c8294280a118d.zip chromium_src-8bf26f49ab4b5fd24fe788e4d64c8294280a118d.tar.gz chromium_src-8bf26f49ab4b5fd24fe788e4d64c8294280a118d.tar.bz2 | |
Http Cache: First pass of byte-range requests support.
This is the first pass to implement support for range
requests and the asociated sparse cache entry.
It is disabled by default, and requires ENABLE_RANGE_SUPPORT
to be defined in order to activate the code: all the code
is compiled in, but Start() bypasses the cache for range
requests, and OnNetworkInfoAvailable ignores 206.
Big parts are still not implemented. Most notably we are
not modifying the response headers that we send to the
user, so the content-range and content-length info
are not correct.
BUG=12258
TEST=Unit tests.
Review URL: http://codereview.chromium.org/118345
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@18289 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/chrome.gyp')
0 files changed, 0 insertions, 0 deletions