Expire but don't clear HostCache on DNS config change

Expire but don't clear HostCache on DNS config change

Before this change, HostCache entries are expired (not cleared) on IP
address changes, but the entire cache is cleared on DNS config changes.
This isn't useful because the distinction is currently only used in an
Android-specific experiment, and all network changes on Android involve
a DNS config change.

Cronet with the stale DNS experiment enabled will now use HostCache
entries from other networks if the allow_other_network option is turned
on. Chrome itself should not have any changes other than keeping more
results in cache that won't be used.

BUG=691078
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_cronet_tester

Review-Url: https://codereview.chromium.org/2785563002
Cr-Commit-Position: refs/heads/master@{#460401}
Committed: https://chromium.googlesource.com/chromium/src/+/92b1af1d8a6162a1a9638d02c3485363ffb60abd

[mgersh, 2017-03-28 21:49:36]

Description was changed from

==========
Expire but don't clear HostCache on DNS config change

Before this change, HostCache entries are expired (not cleared) on IP
address changes, but the entire cache is cleared on DNS config changes.
This isn't useful because the distinction is currently only used in an
Android-specific experiment, and all network changes on Android involve
a DNS config change.

Cronet with the stale DNS experiment enabled will now use HostCache
entries from other networks if the allow_other_network option is turned
on. Chrome itself should not have any changes other than keeping more
results in cache that won't be used.

BUG=691078
==========

to

==========
Expire but don't clear HostCache on DNS config change

Before this change, HostCache entries are expired (not cleared) on IP
address changes, but the entire cache is cleared on DNS config changes.
This isn't useful because the distinction is currently only used in an
Android-specific experiment, and all network changes on Android involve
a DNS config change.

Cronet with the stale DNS experiment enabled will now use HostCache
entries from other networks if the allow_other_network option is turned
on. Chrome itself should not have any changes other than keeping more
results in cache that won't be used.

BUG=691078
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_cronet_tester
==========

[mgersh, 2017-03-28 21:58:57]

mgersh@chromium.org changed reviewers:
+ juliatuttle@chromium.org

[mgersh, 2017-03-28 21:58:57]

Oops. I didn't understand enough of how network changes work when I did
https://codereview.chromium.org/2692043002/ so it still didn't do anything.

[Julia Tuttle, 2017-03-28 22:07:38]

lgtm! Hope it works this time.

[mgersh, 2017-03-29 14:43:20]

The CQ bit was checked by mgersh@chromium.org

[commit-bot: I haz the power, 2017-03-29 14:43:40]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-03-29 15:49:28]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1490798600909220, "parent_rev":
"d8462c3cca625a374bd9ffabb5b23178a53b70e2", "commit_rev":
"92b1af1d8a6162a1a9638d02c3485363ffb60abd"}

[commit-bot: I haz the power, 2017-03-29 15:50:19]

Description was changed from

==========
Expire but don't clear HostCache on DNS config change

Before this change, HostCache entries are expired (not cleared) on IP
address changes, but the entire cache is cleared on DNS config changes.
This isn't useful because the distinction is currently only used in an
Android-specific experiment, and all network changes on Android involve
a DNS config change.

Cronet with the stale DNS experiment enabled will now use HostCache
entries from other networks if the allow_other_network option is turned
on. Chrome itself should not have any changes other than keeping more
results in cache that won't be used.

BUG=691078
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_cronet_tester
==========

to

==========
Expire but don't clear HostCache on DNS config change

Before this change, HostCache entries are expired (not cleared) on IP
address changes, but the entire cache is cleared on DNS config changes.
This isn't useful because the distinction is currently only used in an
Android-specific experiment, and all network changes on Android involve
a DNS config change.

Cronet with the stale DNS experiment enabled will now use HostCache
entries from other networks if the allow_other_network option is turned
on. Chrome itself should not have any changes other than keeping more
results in cache that won't be used.

BUG=691078
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_cronet_tester

Review-Url: https://codereview.chromium.org/2785563002
Cr-Commit-Position: refs/heads/master@{#460401}
Committed:
https://chromium.googlesource.com/chromium/src/+/92b1af1d8a6162a1a9638d02c348...
==========

[commit-bot: I haz the power, 2017-03-29 15:50:20]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/92b1af1d8a6162a1a9638d02c348...