| 127.0.0.1 localhost | 192.168.1.2 woody.lan1 woody # localhost eth0
Yes, and of course i knew that ... However, i couldn't come up with any reason not to do it the other way, and i decided to try just that. My intuition was to use the domain-less 'woody' for local, and append the domain when outward connections are concerned. That time i thought of avoiding to configure servers to accept connections to the often ill-targeted 'localhost', while today i feel more trust in modern servers - when properly configured -, and i also know more about professional attacks which use so many different ways that the existence of 'localhost' doesn't matter anymore, anyway. This was about 4 years ago, and while the environment changed several times i didn't change it, because i couldn't discover the slightest problem so far. So, besides for the really small flaw that 'woody' doesn't mean the same on remote machines, than on the server (but works correctly anyway), which i trade happily for some more peace of mind, do you know any serious argument speaking against this setup ? While it's still unconfirmed that this has anyting to do with the delay loading pages with wwwoffle online. Remember, this setup works since about 4 years, but the delay occured only some weeks ago. ° /\/
