• Possibly linux
      link
      fedilink
      English
      315 months ago

      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

        • 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.

  • @RedWeasel@lemmy.world
    link
    fedilink
    English
    24
    edit-2
    5 months ago

    I just wish they’d stop blocking http requests on lan addresses honestly.

    Thanks for the suggestions. While I was investigating I ended up looking and had a proxy issue. Obviously a problem on my part.

    • 0.0.0.0 binds to all addresses on the machine for servers, but I don’t know what a browser would do when trying to resolve it. I guess look at all addresses on the machine and see if anything has bound to the indicated port on that address? First one it finds wins?

  • Eager Eagle
    link
    fedilink
    English
    85 months ago

    Fine by me. I self-host a lot of stuff but never used 0.0.0.0 for browsing, so I just disabled it here to try it out.

  • @Dave@lemmy.nz
    link
    fedilink
    75 months ago

    The linked blog post explains about the vulnerability, I thought it was quite interesting.