URL fails to resolve
Reported by
dunn.le...@gmail.com,
Nov 11
|
|||||||
Issue descriptionDevice name: nexus 7 From "Settings > About Chrome" Application version: 70.0.3538:80 Operating system: Android 6.0.1 URLs (if applicable): https://link.overdrive.com/?websiteid=290 Steps to reproduce: (1)enter the above URL into the above Chrome for Andriod version (2) (3) Expected result: The URL should resolve to the Washington Anytime Library website, https://anytime.overdrive.com/ Actual result: the following error is displayed on the page: This site can't be reached link.overdrive.com's server IP address could not be found. DNS_PROBE_FINISHED_NXDOMAIN The link works fine on my laptop running Chrome Version 70.0.3538.77 (Official Build) (64-bit) The link works fine on my Fire tablet running Silk version 70.2.2.3538.64.10 This link is part of the Overdrive app. Thank you, Michael Dunn
,
Nov 12
Tested the issue on android and unable to reproduce the issue Steps to reproduce: -------------------------- 1. Launched chrome and navigated to https://link.overdrive.com/?websiteid=290 2. Page navigated to https://anytime.overdrive.com/ Chrome version: 70.0.3538.80 OS: Android 6.0 Android device: Nexus 5 @ dunn.levey: Please check the above steps and let us know if we miss anything. Is this issue consistently reproducible? Is this issue on any other mobile devices? Any information on reproducing the issue would help in better triaging. Thanks!
,
Nov 12
Those are the steps I follow and it fails every time. This problem did not exist before the .80 release at the end of October. The only other difference with your testing is that I am running Android 6.0.1, Nexus 7 Build/MOB30X Please check this combination. Otherwise, is there any other configuration settings that I should check? Thanks for you effort. As a test engineer I understand the complexity of testing the various different combinations of browsers and operating systems. Later, Michael Michael and Ellen 206-276-9720 On Mon, Nov 12, 2018, 1:43 AM chelamch… via monorail < monorail+v2.3282746751@chromium.org wrote:
,
Nov 12
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 12
,
Nov 13
Please collect and attach a chrome://net-export log. Instructions can be found here: https://sites.google.com/a/chromium.org/dev/for-testers/providing-network-details
,
Nov 20
dunn.levey: Are you able to provide a net-export log as described in comment 6?
,
Nov 21
i tried to follow the instructions to create a net-export log and i no longer got the failure message that i had been seeing. so, i went back to the original app where i first started getting this error and it is working correctly. i guess that everything is now working so we are good.
,
Nov 21
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 26
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by chelamcherla@chromium.org
, Nov 12