Skip to content

Should 0.0.0.0 always be a network error? #1117

Open
@annevk

Description

@annevk
Member

See discussion in WICG/private-network-access#24.

(Maybe wait until #1118 is fixed before fixing this.)

Activity

letitz

letitz commented on Feb 24, 2022

@letitz

I'd be in favor of such a move - it makes the web platform more interoperable given that behavior currently differs between OSes.

letitz

letitz commented on May 13, 2022

@letitz

@iVanlIsh has added a use counter to Chrome 102 in order to estimate usage of 0.0.0.0. So far, usage seems pretty low - around 0.002% of total page loads in Beta: https://chromestatus.com/metrics/feature/timeline/popularity/4203. We're waiting to see how the data looks in stable, but it seems that a straight deprecation would be feasible.

added a commit that references this issue on Jul 10, 2024
ca2c938
linked a pull request that will close this issue on Jul 10, 2024
added a commit that references this issue on Aug 19, 2024
eccd05c
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      Participants

      @annevk@letitz

      Issue actions

        Should 0.0.0.0 always be a network error? · Issue #1117 · whatwg/fetch