perf: imprve default host for windows, docker and wsl #126
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
π Linked issue
β Type of change
π Description
Since we had defaulted the host from anyhost to local, there had been several performance issues often either related to the ipv4/ipv6 dual stack or isolated envs (docker and WSL)
With #119 listen changed to prefer ipv4 stack
127.0.0.1
for Windows and WSL, however, it introduced performance regressions for Windows users when users type inlocalhost
in the browser (it takes time from OS to first try::1
as ipv6 localhost and falling back to127.0.0.1
).This PR tries to make behavior more reasonable:
localhost
perfectly works fast in different scenarios""
(anyhost). These are by default isolated environments and need to be exposed by their runtime. Listening on all available interfaces makes it faster.π Checklist