On Mon, Oct 23, 2023 at 02:09:31PM -0400, Greg Wooledge wrote: > On Mon, Oct 23, 2023 at 12:12:50PM -0400, gene heskett wrote: > > > > Google seems to have high jacked port 80 > > > > > > https://lists.debian.org/msgid-search/0a8b96aa-8630-ee5c-5135-59221c55b...@shentel.net > > > > > They have, chromium, the google browser, absolutely cannot be sent to > > http://localhost:80 on any arm system here at the Heskett Ranchette. FF can, > > but not chromium, its doing a failed advertising lookup on google instead. >
Gene, Admittedly on amd64 virtual machine but as a datum point. With Gnome, nginx and Chromium installed - thus a working web server on the same machine Chromium works perfectly to serve http://localhost:80 and serves the nginx page perfectly Cannot reproduce, Andy > I don't have Chromium, but I do have Google Chrome installed. > > ii google-chrome-stable 118.0.5993.88-1 amd64 The web browser from > Google > > Whatever issue you're seeing, I'm not able to reproduce it. If I run > a service on localhost port 80, and then paste http://localhost:80 into > the URL bar in Chrome (copied directly from your email), it connects > to the localhost service. > > unicorn:~$ sudo tcpserver -v 0 80 /usr/bin/printf 'hello world\r\n' > tcpserver: status: 0/40 > tcpserver: status: 1/40 > tcpserver: pid 473439 from 127.0.0.1 > tcpserver: ok 473439 localhost:127.0.0.1:80 localhost:127.0.0.1::45292 > tcpserver: end 473439 status 0 > tcpserver: status: 0/40 > > unicorn:~$ grep localhost /etc/hosts > 127.0.0.1 localhost > ::1 localhost ip6-localhost ip6-loopback > > unicorn:~$ grep hosts /etc/nsswitch.conf > hosts: files mdns4_minimal [NOTFOUND=return] dns > > There's no conspiracy here. There's no "every few years Debian changes > something and I have to scramble to fix it". This stuff just works, Gene. > For everybody except you. >
