• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

127.0.0.1 not localhost

Deeko

Lifer
I need to send a message to my local machine with an ip address (cant be localhost). I see no problem with using 127.0.0.1 but my boss claims the network admin could change it. Anyway, is this actually possible, or am I safe using it?
 
not sure what you're actually trying to accomplish. 127.0.0.1 is non-routable, rather used for testing purposes...
 
I have to send a message to my local machine via the message queue, there is a trigger set up that I need fired. Last time I tried sending anything via message queueing with a host name, not an IP, it didn't work, just sat in the outgoing queue.
 
your boss is full of it.

127.0.0.1 is always the local host and cannot be changed. Unless of course your boss believes he has the power to rewrite the RFCs, call up ARIN and ICANN and get the entire Internet changed to suit his fancy.
 
"localhost" is, by definition, 127.0.0.1 which is a non-routable address. You should be fine.

Dave

Edit: In general, your boss is correct in that you don't want to hardwire your application(s) to specific IP addresses as they can change without any notice. But the localhost address is a special one (and CAN'T change) so that rule doesn't apply.
 
you could also make sure your hosts file has the correct entry of:
localhost 127.0.0.1
at least that way you can determine if there is some other reason why your application is not resolving "localhost" properly
 
Back
Top