Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #260581
| From | Darac Marjal <mailinglist@darac.org.uk> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: chrome web browser worthless |
| Date | 2023-08-02 10:00 +0200 |
| Message-ID | <GYeVX-4xp1-1@gated-at.bofh.it> (permalink) |
| References | <GXU1b-4gfe-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
[Multipart message — attachments visible in raw view] - view raw
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.
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll 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