Timeline for How & why do "0.0.0.0" connections get a response?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 11, 2019 at 8:30 | comment | added | CyberSkull |
launchd can be configured to act as a super server and it could be the program the 0.0.0.0 requests are being routed to.
|
|
| Aug 11, 2019 at 7:02 | comment | added | WGroleau | Yeah, I guess just removing that file and doing a 404 (or 500, in case the firewall leaks) would be good enough. | |
| Aug 11, 2019 at 6:07 | comment | added | Gordon Davisson | @WGroleau Having Apache serve mostly-empty 404 messages shouldn't be much load, and will prevent the browser pausing waiting for timeouts. If you do firewall it, make sure it sends some sort of reject packet to cause an immediate connection failure, rather than just dropping the connection and letting it time out. | |
| Aug 11, 2019 at 4:50 | comment | added | WGroleau | I run Apache because I have local copies of a couple of websites. But I don't recall doing anything to configure that … checking … (sheepish grin) … sure enough, that is the contents of index.html.en with a rather old mod date on it! Don't know why I did that, as I've disabled http(s) connections from outside. So, in order to keep links to those domains from using Apache CPU time, I have to firewall that IP, or use one that can't do anything. Maybe a block A address, since everything here is 168.x.x.x? | |
| Aug 11, 2019 at 4:47 | vote | accept | WGroleau | ||
| Aug 11, 2019 at 3:59 | history | answered | Gordon Davisson | CC BY-SA 4.0 |