test: specify explicit non-numeric hosts in tests
All-numeric domains are now considered invalid, since they introduce confusion: one can assume that an all-numeric domain is a port, and the server should bind to `localhost` with that port. The specific change to domain parsing happens in a future commit. This commit fixes the tests in preparation for it. Note that all-numeric top-level domains are considered invalid according to RFC 952 and RFC 1123. In fact, the top-level domain label must be alphabetic, but we do not place that restriction, since local domains could have arbitrary format.
Showing
- src/address.rs 6 additions, 14 deletionssrc/address.rs
- src/config.rs 5 additions, 5 deletionssrc/config.rs
- test/int/test_cli_connect.py 6 additions, 6 deletionstest/int/test_cli_connect.py
- test/int/test_expelling.py 1 addition, 1 deletiontest/int/test_expelling.py
- test/int/test_uninitialized.py 1 addition, 1 deletiontest/int/test_uninitialized.py
Loading
Please register or sign in to comment