http://www.perlmonks.org?node_id=1227888


in reply to Re^2: Difficulties with WWW::Mechanize::Chrome installation on Windows/Strawberry
in thread Difficulties with WWW::Mechanize::Chrome installation on Windows/Strawberry

http://search.frontier.com/search/?q=http://somewhere.example/myif +rame&t=0
Ahh. It's not actually on my system: the same thing happens both on my phone thru WiFi at home, or on my PC. Based on the URL of frontier.com, my ISP is apparently "helping me" by injecting their search when I try to go to a domain that doesn't exist -- probably because I'm using their DNS.

Aah, I see now. Maybe I can change that to a different, non-existing domain that does not get served by them. Maybe using localhost with a port number that is hopefully unused will work better, or have a different failure mode at least ...

Replies are listed 'Best First'.
Re^4: Difficulties with WWW::Mechanize::Chrome installation on Windows/Strawberry
by kschwab (Vicar) on Jan 01, 2019 at 19:56 UTC
    http://0.0.0.0/ might be a good option. Chrome bombs with "ERR_ADDRESS_INVALID" when you navigate there.

      Thanks!

      I'm currently testing moving all "invalid" addresses to https, maybe that works well enough, otherwise, 0.0.0.0 is the next stop :)

Re^4: Difficulties with WWW::Mechanize::Chrome installation on Windows/Strawberry
by pryrt (Monsignor) on Jan 01, 2019 at 20:06 UTC

    Okay, I pointed my router at google's DNS instead of Frontier's DNS. I did a fresh berrybrew install of 5.28.1, and ran

    cpanm --installdeps AnyEvent => success cpanm AnyEvent => success (hmm) cpanm --installdeps Log::Log4perl => success cpanm Log::Log4perl => failure (known issue) cpanm --notest Log::Log4perl => installed cpanm --installdeps WWW::Mechanize::Chrome => passed all but Future:: +HTTP cpanm --installdeps Future::HTTP => success cpanm Future::HTTP => success (sometimes the order of + installs influences) cpanm --installdeps WWW::Mechanize::Chrome => success cpanm WWW::Mechanize::Chrome => success

    So, yes, changing to Google DNS fixed the issue with the WWW::Mechanize::Chrome test suite itself. Submitting passing report to cpantesters to offset my failure