[Cronet] Add option to use stale DNS when network resolver returns ERR_NAME_NOT_RESOLVED
Sometimes resolving a host name will result in ERR_NAME_NOT_RESOLVED even though the host still should resolve. This change adds an option to use stale DNS results in these cases. Bug: 875845 Cq-Include-Trybots: master.tryserver.chromium.android:android_cronet_tester;master.tryserver.chromium.mac:ios-simulator-cronet Change-Id: I02b7a122bb9236f9ff47c73af8e4803315dcd382 Reviewed-on: https://chromium-review.googlesource.com/1179998 Commit-Queue: Paul Jensen <pauljensen@chromium.org> Reviewed-by:Misha Efimov <mef@chromium.org> Cr-Commit-Position: refs/heads/master@{#584772}
Showing
Please register or sign in to comment