Re: chrome web browser worthless

[Darac Marjal <mailinglist@darac.org.uk>]

On 01/08/2023 10:33, gene heskett wrote:
> Google seems to have high jacked port 80, I cannot use it as a browser 
> to run klipper as a google search intercepts port 80, so localhost:80 
> cannot be used for troubleshooting or for running a 3d printer with 
> klipper..

I think this comes down to an ambiguity in how Chrome parses the input:

* "Pictures of Cats" - Clearly not a URI, so pass it to the default 
search engine

* "http://http.cat/302"; - Clearly a URI, so navigate to it

* "localhost:80" - This is ambiguous

In the case of the latter, are you wanting to use the localhost scheme 
to access the resource called 80 (now, you're going to say "There is no 
protocol called localhost" and I think that Chrome used to know which 
protocols exist but now it's a bit more agnostic)?


Try being explicit about the scheme (i.e. type "http://localhost:80";) 
and see if Chrome is happier.


> FF has no such problems.
>
> Cheers, Gene Heskett.

Attachment: OpenPGP_signature
Description: OpenPGP digital signature