Nemeski to Firefox@lemmy.ml • edit-21 year agoFirefox Blocks 0.0.0.0 IP Addresses: Tell Us What This Means To You!connect.mozilla.orgexternal-linkmessage-square31fedilinkarrow-up196arrow-down12 cross-posted to: firefox@lemmy.world
arrow-up194arrow-down1external-linkFirefox Blocks 0.0.0.0 IP Addresses: Tell Us What This Means To You!connect.mozilla.orgNemeski to Firefox@lemmy.ml • edit-21 year agomessage-square31fedilink cross-posted to: firefox@lemmy.world
minus-squarePossibly linuxlinkfedilinkEnglish32•1 year 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-squareTaasz/WooflinkfedilinkEnglish14•1 year agoYeah I’m familiar with that part, I just meant in context of a browser being able to connect to it.
minus-square@sugar_in_your_tea@sh.itjust.workslinkfedilink2•1 year 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.