Nemeski@lemm.ee to Firefox@lemmy.ml · edit-23 days agoFirefox Blocks 0.0.0.0 IP Addresses: Tell Us What This Means To You!connect.mozilla.orgexternal-linkmessage-square33fedilinkarrow-up191arrow-down11
arrow-up190arrow-down1external-linkFirefox Blocks 0.0.0.0 IP Addresses: Tell Us What This Means To You!connect.mozilla.orgNemeski@lemm.ee to Firefox@lemmy.ml · edit-23 days agomessage-square33fedilink
minus-squarePossibly linux@lemmy.ziplinkfedilinkEnglisharrow-up32·3 days agoOn Linux it is just a catch all address (listen on all interfaces) Elsewhere it doesn’t do anything since I don’t believe it is part of the networking standards
minus-squareMangoPenguin@lemmy.blahaj.zonelinkfedilinkEnglisharrow-up14·3 days agoYeah I’m familiar with that part, I just meant in context of a browser being able to connect to it.
minus-squaresugar_in_your_tea@sh.itjust.workslinkfedilinkarrow-up2·2 days agoIf I were implementing it, I’d just list all interfaces on the machine and see if there’s a service bound to it on the given port. There’s probably only one, but it’s technically undefined behavior I think.
On Linux it is just a catch all address (listen on all interfaces)
Elsewhere it doesn’t do anything since I don’t believe it is part of the networking standards
Yeah I’m familiar with that part, I just meant in context of a browser being able to connect to it.
If I were implementing it, I’d just list all interfaces on the machine and see if there’s a service bound to it on the given port. There’s probably only one, but it’s technically undefined behavior I think.