On Jan 3, 2015, at 3:41 PM, William H. Magill wrote: > >> Did Apple change something in Yosemite/Safari so that "localhost" is no >> longer an accessible DNS address for Safari? >> >> I have no trouble ssh-ing to localhost on my system, but Safari always >> responds "Can't connect to the Server." >> >> Note that at one time I was using Apple's Apache via OSX Server, but have >> since replaced that with MacPorts. >> And, I have no idea if "localhost" worked after I upgraded to Yosemite and >> OSX Server ceased operation.
Interesting set of replies (below). What triggered my query was the fact that various "how to" pages describe using "localhost" as a mechanic for testing certain web based services -- which did not work! https://trac.macports.org/wiki/howto/Apache2 I'm guessing that the over-arching description that one can define "ServerName localhost:80" is simply no longer an "appropriate" statement for OSX and Yosemite. And apparently for Apache2 in general -- it works and passes validation, but the results of its use are not predictable. It also appears that the function of the ServerName directive has changed. The current Apache manual http://httpd.apache.org/docs/2.2/mod/core.html#servername describes its syntax as requiring a FQDN -- which neither Localhost nor IP address constructs (127.0.0,1) really are. (Apparently the directive is directly related to various DOS, Virtual Host and other DNS issues and is supplanted by the results from "gethostname" C function. http://httpd.apache.org/docs/2.2/dns-caveats.html In short, it appears that the old "localhost" shortcut needs to disappear from the documentation. For no other reason than the fact that results from using it are not reproducible. I hate documentation which states "do X for result Y" -- only to get result Z when you do so! All of which is compounded by the fact that while Yosemite "will work" if you are not connected to the Internet, Apple has structured things such that Yosemite EXPECTS to be connected to the Internet, i.e "the iCloud." On Jan 3, 2015, at 7:45 PM, Ryan Schmidt <ryandes...@macports.org> wrote: > > I experience the problem on Yosemite that "localhost" will randomly switch > between accessing the IPv4 address of my server (which works) and the IPv6 > address of my server (which apparently isn't working). I've had to start > using "127.0.0.1" instead, which is the IPv4 address. This does not appear to > be specific to Safari; I saw it in the terminal with curl too. On Jan 3, 2015, at 7:49 PM, Richard L. Hamilton <rlha...@smart.net> wrote: > > You might try > > http://127.0.0.1/ > and > http://[::1]/ > > (IPv4 and IPv6 addresses for localhost - use https and a port number if > required) If neither of those works either, it’s probably not the hostname > lookup (which is not necessarily just DNS, depending on how you’re > configured). > > Safari should be able to look up localhost from other than DNS (/etc/hosts or > local OpenDirectory storage, I think) anyway.. On Jan 3, 2015, at 7:51 PM, Dave Horsfall <d...@horsfall.org> wrote: > > > I've seen it in Firefox from time to time, when my MacBook's FF refreshes > itself against the pages on my FreeBSD server (which happens to support > IPv6 as well, but it shows in the Apache logs). On Jan 3, 2015, at 8:00 PM, René J.V. Bertin <rjvber...@gmail.com> wrote: > I experience the problem on Yosemite that "localhost" will randomly switch > between accessing the IPv4 address of my server (which works) and the IPv6 > address of my server (which apparently isn't working). I've had to start > using "127.0.0.1" instead, which is the IPv4 address. This does not appear to > be specific to Safari; I saw it in the terminal with curl too. I had similar issues a long time ago already, already back in October 2006 I commented out the line with the IPv6 localhost address in /etc/hosts. I've never noticed any side-effects, and using IPv6 when you're behind a router that probably assigns addresses from a private netblock like 192.168.0.0/16 is completely unnecessary. I've never tried, but it might be enough to deactivate IPv6 support in the Network Location settings if you prefer not to touch /etc/hosts. T.T.F.N. William H. Magill mag...@icloud.com mag...@mac.com whmag...@gmail.com _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
