You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
t5516/t5601: avoid using localhost for failing HTTPS requests
In 6dcbdc0 (remote: create fetch.credentialsInUrl config,
2022-06-06), we added four test cases that validate various behavior
around passing credentials as part of the URL (which is considered
unsafe in general).
These tests do not _actually_ try to connect anywhere, but have to use
the https:// protocol in order to validate the intended code paths.
However, using `localhost` for such a connection causes several
problems:
- There might be a web server running on localhost, and we do not
actually want to connect to that.
- The DNS resolver, or the local firewall, might take a substantial
amount of time (or forever, whichever comes first) to fail to connect,
slowing down the test cases unnecessarily.
Let's instead use an IPv4 address that is guaranteed never to offer a
web server: 224.0.0.1 (which is part of the IP multicast range).
Incidentally, this seems to fix an issue where the tests fail in the
Windows jobs of Git's CI builds.
Signed-off-by: Johannes Schindelin <[email protected]>
0 commit comments