Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Should 0.0.0.0 always be a network error? #1117

Open
annevk opened this issue Nov 30, 2020 · 2 comments · May be fixed by #1763
Open

Should 0.0.0.0 always be a network error? #1117

annevk opened this issue Nov 30, 2020 · 2 comments · May be fixed by #1763

Comments

@annevk
Copy link
Member

annevk commented Nov 30, 2020 •
edited
Loading

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

(Maybe wait until #1118 is fixed before fixing this.)
@annevk annevk mentioned this issue Feb 24, 2022
Open
@letitz
Copy link

letitz commented Feb 24, 2022

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

@letitz
Copy link

letitz commented May 13, 2022

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

@mcodik mcodik mentioned this issue Nov 3, 2022
Open
annevk added a commit that referenced this issue Jul 10, 2024
@annevk
Block access to 0.0.0.0
ca2c938 
Fixes #1117.
@annevk annevk linked a pull request Jul 10, 2024 that will close this issue
Open
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Block access to 0.0.0.0 whatwg/fetch
2 participants
@annevk @letitz