3 ms·
Can anybody with more knowledge point out techniques that this would break? Are there any software or networking patterns that currently rely on localhost _not
by eduren 9y ago
Can anybody with more knowledge point out techniques that this would break?
Are there any software or networking patterns that currently rely on localhost _not_ resolving to the loopback?
EDIT: The RFC mentions that MySQL currently differentiates between the two, but that's it.
- mschuster91 9y agoHmm I guess people may use IPs other than 127.0.0.1 like 127.0.0.2 for Docker or maybe VPN/VM shenanigans...
- inopinatus 9y agoThis remains valid under the draft.
- hazeii 9y agoWithin ".localhost."... www.localhost.mydomain.com?
- xnxn 9y agoThe trailing "." signifies the end of the domain name, so your example domain would be unaffected.
- mnarayan01 9y ago> Application software MUST NOT use a searchlist to resolve a localhost name.
- deleted 9y ago[deleted]
- hazeii 9y agoThanks, I misread the draft as '<star>.localhost.<star>'(!)
- mnarayan01 9y agoAnyone using DNS search lists to have localhost resolve to e.g. localhost.example.com would potentially have problems. Obviously this is a pretty weird thing to intentionally do, but it currently gives you a quick way to get around certain issues. Obviously this is ugly, but in some ways that actually makes breaking it more problematic: Things which this breaks are likely to be things that are difficult to fix.