Re: chrome web browser worthless

From	gene heskett <gheskett@shentel.net>
Newsgroups	linux.debian.user
Subject	Re: chrome web browser worthless
Date	2023-08-02 20:50 +0200
Message-ID	<GYp4Z-4EvH-3@gated-at.bofh.it> (permalink)
References	<GXU1b-4gfe-1@gated-at.bofh.it> <GYeVX-4xp1-1@gated-at.bofh.it> <GYi3v-4zJh-5@gated-at.bofh.it> <GYnwe-4DBj-9@gated-at.bofh.it> <GYnPz-4DJn-13@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On 8/2/23 13:21, Greg Wooledge wrote:
> On Wed, Aug 02, 2023 at 01:07:13PM -0400, gene heskett wrote:
>> On 8/2/23 07:14, Greg Wooledge wrote:
>>> On Wed, Aug 02, 2023 at 08:43:32AM +0100, Darac Marjal wrote:
>>>> * "localhost:80" - This is ambiguous
>>>>
>> [...]
>>>
>>> It would be nice if we had an exact recipe for how to reproduce the
>>> problem.  Failing that, it'll be up to Gene to debug the situation on
>>> his end.  I'm still leaning toward an edited /etc/hosts file.
>>>
>>
>> At this point Greg, I'll plead guilty to a hand edited /etc/hosts file.
>> So here it is, tell me whats wrong:
>>
>> gene@bpi52:~$ cat /etc/hosts
>> 127.0.0.1       localhost
>>
>> There is more of course but the rest of it is private local network
>> (192.168.xxx.yyy) addresses of no concern here.
> 
> Well, that looks reasonable.  You're missing the IPv6 entry, but that
> probably doesn't matter.  So, assuming there are no other occurrences
> of the word "localhost", whatever is causing the problem probably
> lies elsewhere.
> 
> Did you attempt any other diagnostics?  Typing the full URL including
> the http:// part, or launching Chrome with a new profile?  Are you able
> to reproduce the problem consistently, and if so, how?  What are the
> exact symptoms you see?
> 
> Another thing to try, which I forgot to mention last time, would be using
> the IP address directly:  http://127.0.0.1/   That bypasses any hostname
> lookup issues that may exist.  It's pretty unlikely that a web service
> running on localhost would care whether you addressed it by name or by IP
> address (virtual hosts on loopback are not commonplace AFAIK).
> 
Its idle atm, so I'll give that a shot, brb. A click on the empty 
address line gets me a menu from google. this pops up with the first 
character typed, but if I continue with //127.0.0.1:80, I see a ; 
replacing the : and the 80 disappears but it does work, and I am looking 
at the klipper web page, used to run the printer. And everything seems 
to work.  And work about 3x faster after I had used one of 
klipper/mainsail's options to check and update first the OS, and then 
all of kiauh. Screen response is around 3 or 4x faster, both on its own 
screen and with FF watching it at bpi52:80 from here.  A welcome speedup.

Thanks fpr the hint, Greg, very useful.
> .

Cheers, Gene Heskett.
-- 
"There are four boxes to be used in defense of liberty:
  soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
  - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>

Thread

chrome web browser worthless gene heskett <gheskett@shentel.net> - 2023-08-01 11:40 +0200
  Re: chrome web browser worthless Bret Busby <bret@busby.net> - 2023-08-01 12:30 +0200
    Re: chrome web browser worthless gene heskett <gheskett@shentel.net> - 2023-08-01 15:00 +0200
      Re: chrome web browser worthless Bret Busby <bret@busby.net> - 2023-08-01 18:40 +0200
  Re: chrome web browser worthless Phil Wyett <philip.wyett@kathenas.org> - 2023-08-01 12:30 +0200
    Re: chrome web browser worthless gene heskett <gheskett@shentel.net> - 2023-08-01 14:20 +0200
      Re: chrome web browser worthless "Andrew M.A. Cater" <amacater@einval.com> - 2023-08-01 14:40 +0200
  Re: chrome web browser worthless Greg Wooledge <greg@wooledge.org> - 2023-08-01 13:30 +0200
  Re: chrome web browser worthless "Roy J. Tellason, Sr." <roy@rtellason.com> - 2023-08-01 22:20 +0200
  Re: chrome web browser worthless Darac Marjal <mailinglist@darac.org.uk> - 2023-08-02 10:00 +0200
    Re: chrome web browser worthless Greg Wooledge <greg@wooledge.org> - 2023-08-02 13:20 +0200
      Re: chrome web browser worthless Stefan Monnier <monnier@iro.umontreal.ca> - 2023-08-02 15:50 +0200
        Re: chrome web browser worthless gene heskett <gheskett@shentel.net> - 2023-08-02 20:10 +0200
          Re: chrome web browser worthless Andy Smith <andy@strugglers.net> - 2023-08-02 21:10 +0200
            Re: chrome web browser worthless Brian <ad44@cityscape.co.uk> - 2023-08-02 21:50 +0200
      Re: chrome web browser worthless gene heskett <gheskett@shentel.net> - 2023-08-02 19:10 +0200
        Re: chrome web browser worthless Greg Wooledge <greg@wooledge.org> - 2023-08-02 19:30 +0200
          Re: chrome web browser worthless gene heskett <gheskett@shentel.net> - 2023-08-02 20:50 +0200
            Re: chrome web browser worthless David Wright <deblis@lionunicorn.co.uk> - 2023-08-03 07:20 +0200
        Re: chrome web browser worthless Brian <ad44@cityscape.co.uk> - 2023-08-02 20:30 +0200
          Re: chrome web browser worthless gene heskett <gheskett@shentel.net> - 2023-08-02 21:00 +0200
            Re: chrome web browser worthless Brian <ad44@cityscape.co.uk> - 2023-08-02 21:20 +0200
              Re: chrome web browser worthless Greg Wooledge <greg@wooledge.org> - 2023-08-02 21:20 +0200
                Re: chrome web browser worthless gene heskett <gheskett@shentel.net> - 2023-08-02 22:20 +0200
                Re: chrome web browser worthless Brian <ad44@cityscape.co.uk> - 2023-08-02 22:50 +0200
              Re: chrome web browser worthless Lee <ler762@gmail.com> - 2023-08-02 21:40 +0200
              Re: chrome web browser worthless gene heskett <gheskett@shentel.net> - 2023-08-02 22:10 +0200
                Re: chrome web browser worthless Brian <ad44@cityscape.co.uk> - 2023-08-02 23:10 +0200
                Re: chrome web browser worthless gene heskett <gheskett@shentel.net> - 2023-08-03 02:10 +0200
                Re: chrome web browser worthless <tomas@tuxteam.de> - 2023-08-03 06:40 +0200
                Re: chrome web browser worthless gene heskett <gheskett@shentel.net> - 2023-08-03 03:10 +0200
                127.0.1.1 line, was Re: chrome web browser worthless David Wright <deblis@lionunicorn.co.uk> - 2023-08-03 01:30 +0200
                Re: 127.0.1.1 line, was Re: chrome web browser worthless Greg Wooledge <greg@wooledge.org> - 2023-08-03 01:40 +0200
                Re: 127.0.1.1 line, was Re: chrome web browser worthless jeremy ardley <jeremy.ardley@gmail.com> - 2023-08-03 01:50 +0200
                Re: 127.0.1.1 line, was Re: chrome web browser worthless David Wright <deblis@lionunicorn.co.uk> - 2023-08-03 06:30 +0200
                Re: 127.0.1.1 line, was Re: chrome web browser worthless David Christensen <dpchrist@holgerdanske.com> - 2023-08-03 04:10 +0200
                Re: 127.0.1.1 line, was Re: chrome web browser worthless Greg Wooledge <greg@wooledge.org> - 2023-08-03 04:10 +0200
                Re: 127.0.1.1 line, was Re: chrome web browser worthless David Christensen <dpchrist@holgerdanske.com> - 2023-08-04 01:00 +0200
                Re: 127.0.1.1 line, was Re: chrome web browser worthless David Wright <deblis@lionunicorn.co.uk> - 2023-08-05 04:30 +0200
                Re: 127.0.1.1 line, was Re: chrome web browser worthless David Christensen <dpchrist@holgerdanske.com> - 2023-08-05 10:20 +0200
                Re: 127.0.1.1 line, was Re: chrome web browser worthless David Christensen <dpchrist@holgerdanske.com> - 2023-08-03 04:10 +0200

csiph-web