LWP apparently will also self report a 500 status if the connection fails for any reason. The first suggestion would be to add lots of debugging to the perl script to dump its internal state at various points and also snoop on the connection.
I would also check to see if the malfunctioning router is utilizing a proxy of some form. Some tools are able to pick up on a proxy if the OS has automatically put in the appropriate environmental variables but I don't believe LWP can do that. (Curl does look for the environment variables and most browsers can query the OS for proxy information). Admittedly it would be very odd to have a proxy running on a basic router but not impossible. On 2019-04-13 07:59, David Carlson wrote: > There must be something else going on that hasn't been found yet. > > David Carlson > > On Sat, Apr 13, 2019, 9:18 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 _______________________________________________ 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.
