summaryrefslogtreecommitdiffstats
path: root/sandbox
diff options
context:
space:
mode:
authorjar@google.com <jar@google.com@0039d316-1c4b-4281-b951-d872f2087c98>2008-12-05 01:51:30 +0000
committerjar@google.com <jar@google.com@0039d316-1c4b-4281-b951-d872f2087c98>2008-12-05 01:51:30 +0000
commit4c7073f666fd6c0209e1e9ae87e53698371ed973 (patch)
tree708984b8c463a1e4b08f40b64ed06db0b43b13d0 /sandbox
parenta98662d79f3890dfb3eaed7e01e12f46c3b7c4dc (diff)
downloadchromium_src-4c7073f666fd6c0209e1e9ae87e53698371ed973.zip
chromium_src-4c7073f666fd6c0209e1e9ae87e53698371ed973.tar.gz
chromium_src-4c7073f666fd6c0209e1e9ae87e53698371ed973.tar.bz2
Correctly handle (and log) receipt of gzip response to SDCH encode proposal
When the only response to a SDCH encoding proposal (including a statement of an Avail-Dict) is a gzip response, the filtering infrastructure needs to add in a missing "sdch" sniffing filter. This filter should enter into pass-through mode if the content does not have a valid SDCH header. This functionality is critical to the latency experiment, which will signal the fact that a session is in the control group by doing exactly the above pattern (only using gzip, despite the dictionary). This is a blocker for the Chrome SDCH latency experiment. bug = 1520081 reviewers= huanr,openvcdiff,kmixter Review URL: http://codereview.chromium.org/12964 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@6415 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'sandbox')
0 files changed, 0 insertions, 0 deletions