Hostname/IP validation is too strict
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.3k
- Forks
- 959
- Avg merge
- 5d 10h
- Merged PRs (30d)
- 2
Description
If I want to use raphimc.net_25564_1.8.x.viaproxy.127-0-0-1.nip.io:25568 as a hostname for my backend server in the velocity config it complains that the address is not valid. Pinging raphimc.net_25564_1.8.x.viaproxy.127-0-0-1.nip.io in cmd resolves to localhost as it should. The reason I want to use such a long hostname is to pass on information (Through the address in the handshake packet) to the "backend server" (Another proxy) to know where to connect to. Trying to connect to that address with a minecraft client works fine.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file or test is named in the issue. Start by locating Velocity's hostname/IP validation for backend server addresses and reproduce the rejection with the provided nip.io hostname; done means the address is accepted while valid hostname and IP checks continue to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100