Data reduction proxy should not fetch a new config if a fetch is already in progress |
||
Issue descriptionData reduction proxy should not fetch a new config if a fetch is already in progress. Currently, it is possible that a fetch is started due to IP address change. Then, if an AuthFailure is received,a new config fetch would be triggered. The second config fetch will unnecessarily cancel the first ongoing config fetch. This can potentially cause increased data usage, and also increase the time taken for data reduction proxy to acquire a valid config.
,
Jan 3 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/0216e584179ebe2e4ca415930b916f2e76f1b559 commit 0216e584179ebe2e4ca415930b916f2e76f1b559 Author: tbansal <tbansal@chromium.org> Date: Tue Jan 03 19:15:30 2017 Do not fetch a new config if one is already in progress. Do not fetch a data reduction proxy config due to auth failure if the fetch of the previous config is ongoing. BUG= 677569 Review-Url: https://codereview.chromium.org/2604293002 Cr-Commit-Position: refs/heads/master@{#441179} [modify] https://crrev.com/0216e584179ebe2e4ca415930b916f2e76f1b559/components/data_reduction_proxy/core/browser/data_reduction_proxy_config_service_client.cc [modify] https://crrev.com/0216e584179ebe2e4ca415930b916f2e76f1b559/components/data_reduction_proxy/core/browser/data_reduction_proxy_config_service_client.h [modify] https://crrev.com/0216e584179ebe2e4ca415930b916f2e76f1b559/components/data_reduction_proxy/core/browser/data_reduction_proxy_config_service_client_unittest.cc
,
Jan 3 2017
|
||
►
Sign in to add a comment |
||
Comment 1 by tbansal@chromium.org
, Dec 29 2016