Thanks David, Does the corresponding curl command work from your other computers as well? Any suggestions what “coercing” involved in your case?
Best, Bruno > On Apr 22, 2019, at 6:48 PM, David Carlson <david.carlson....@gmail.com> > wrote: > > I too use ATT&T Uverse as my ISP and i know they do have some strange > settings in their router, but the basic firewall and TCP port settings out of > the box are fine for most users without tinkering with pinholes or other > firewall settings. In my neighborhood they now set IPV6 as preferred > addressing protocol. I have several Windows and Linux real or virtual > computers including a few with GnuCash 2.6.17 or 19, but I have only managed > to coerce one of them to download price quotes, and then only when running in > a local desktop but not in a remote terminal. > > I do not know enough about networking to be able to say whether you have a > problem with your router or firewall. > > David Carlson > > > On Mon, Apr 22, 2019, 3:16 PM Bruno Acklin <back...@gmail.com > <mailto:back...@gmail.com>> wrote: > Wow, thanks all for your thoughts, although unfortunately this remains an > unsolved mystery to me! > > Tools/"Price Editor"/"Get Quotes" still works smoothly when I disconnect the > ethernet cable to my router (standard ATT Uverse DSL router and configuration > with DNS 68.94.156.1 and ..157.1) and use wifi to my neighbors router (cable > based), and vice versa not if I reconnect my ethernet. > > [@David] So definitely different ISP, DNS, etc for the two paths. > > [@AC] I did not see any proxy information on my routers broadband status. > <"LWP apparently will also self report a 500 status if the connection fails > for any reason"> I also “interpreted" the 500 error as a sort of timeout > error, because the response comes only after a second or two while it is > instantaneous with curl or browser. > > [@Ronal, ..] I checked for open TCP ports using loopback address 127.0.0.1 > (Is this the right way?). Received identical responses for both paths, > including Port 88 (but not 80!). > > In looking at my firewall settings I noticed that “the computer that will > host applications through the firewall” is still set to my old Time Machine > router (which I assume still runs its own firewall which used to work fine > for gnc-fc before). Should that be set to my desktop? > > I am assuming that a server response to an http: call is governed by > “outgoing protocol control” rules, and does not need any inbound protocol > control enabled, correct? > > Thanks and best, > Bruno > > > On Apr 13, 2019, at 12:41 PM, Adrien Monteleone > > <adrien.montele...@lusfiber.net <mailto:adrien.montele...@lusfiber.net>> > > wrote: > > > > 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 > >> <mailto: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 <mailto: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 > >>>> <mailto: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 <mailto:gnucash-user@gnucash.org> > > To update your subscription preferences or to unsubscribe: > > https://lists.gnucash.org/mailman/listinfo/gnucash-user > > <https://lists.gnucash.org/mailman/listinfo/gnucash-user> > > If you are using Nabble or Gmane, please see > > https://wiki.gnucash.org/wiki/Mailing_Lists > > <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. > > _______________________________________________ > gnucash-user mailing list > gnucash-user@gnucash.org <mailto:gnucash-user@gnucash.org> > To update your subscription preferences or to unsubscribe: > https://lists.gnucash.org/mailman/listinfo/gnucash-user > <https://lists.gnucash.org/mailman/listinfo/gnucash-user> > If you are using Nabble or Gmane, please see > https://wiki.gnucash.org/wiki/Mailing_Lists > <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. _______________________________________________ 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.
