It doesn’t make any sense to me either. But curl works, perl doesn’t. What does that perl script actually do when it tries to pull that URL?
Regards, Adrien > On Apr 13, 2019, at 9:17 AM, John Ralls <jra...@ceridwen.us> wrote: > > The URL is given several times in the thread, it's http, port 80. That aside, > get real: A firewall that blocks a port when perl's LWP is the agent but not > when curl or a web browser is? > > Besides, the request isn't blocked, it's munged so that Yahoo! returns a > 500--server error response. So we have to imagine that the router can somehow > tell that the packets are coming from curl and not messing with them or perl > LWP and messing with them? That's a pretty amazing firewall. > > Regards, > John Ralls > >> On Apr 13, 2019, at 2:32 AM, Adrien Monteleone >> <adrien.montele...@lusfiber.net> wrote: >> >> More likely a blocked port though since the OP said curl works to retrieve >> the same URL, but not perl. A look at the perl script will probably expose >> the issue. >> >> Regards, >> Adrien >> >>> On Apr 13, 2019, at 4:29 AM, David Carlson <david.carlson....@gmail.com> >>> wrote: >>> >>> A different router could also mean a different ISP, a different DNS, and >>> that is just the starting point... >>> >>> David Carlson >>> _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user If you are using Nabble or Gmane, please see https://wiki.gnucash.org/wiki/Mailing_Lists for more information. ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
