jearle@23x# curl -sI apple.com HTTP/1.1 301 MOVED PERMANENTLY
Server: Date: Referer: Location: http://www.apple.com/ Content-type: text/html Connection: close So, apple.com is supposed to redirect to www.apple.com and, surprise surprise, it does. That's how it works. — Sent from Mailbox for iPad On Sun, Oct 27, 2013 at 8:37 PM, William H. Magill <[email protected]> wrote: > On Oct 26, 2013, at 4:56 PM, Jerry Levan <[email protected]> wrote: >> >> Does Safari do something wonky with name to ip lookups? > From what I can tell, the answer is a definite -- Yes. > I can't tell you how many times I have typed incorrect or incomplete "names" > and have had them "work, as expected" although not correctly. > (Especially true for websites I have previously visited.) > One presumes that this is part and parcel of the "make this a 'user friendly' > experience" concept. > Easy example -- type "apple.com" and you go to "www.apple.com" -- instead of > failing, as it should. > (And these situations are NOT my ISP being "helpful" -- that brings up a > separate page of "suggestions.") > Short of "reseting" Safari, I don't know WHERE to find the information it is > using. I suppose that deleting ~Library/caches/com.apple.safari* (there are > several) and > ~Library/Safari and ~Library/preferences/com.apple.safari* (again there are > multiple) -- is equivalent to using the drop-down "Reset", but I don't know. > As for the loss of the various Nameserver software... > This doesn't surprise me. Those files were likely in "system directories" -- > the Upgrade to a new OS release tends to simply "overwrite" those things > which the user is not supposed to be modifying.... resetting them to the > "Apple Way." > This is undoubtedly compounded by the fact that 10.9 is NOT compatible with > earlier versions of OSX Server, and requires you to install a new (and > charged for) version of OSX Server. Meaning -- the Update installer "knows" > that all those BIND related directories have to be "updated," so it's best to > just make them go away. > And for what it's worth. I would strongly recommend using OSX Server for your > name service. It works, is kept current with security patches, and is simply > easier to deal with than using MacPorts! > BTW... for whatever reason the AppStore is "supposed" to provide the Command > Line tools for use with Xcde 5.0.1. However, it seems to (still) be failing > "not available"... simply download them from the Developer's download page. > T.T.F.N. > William H. Magill > # iMac11,3 Core i7 [2.93GHz - 8 GB 1067MHz] OS X 10.9 > # Macmini6,1 Intel Core i5 [2.5 Ghz - 4GB 1600MHz] OS X 10.8.5 > [email protected] > [email protected] > [email protected] > _______________________________________________ > MacOSX-admin mailing list > [email protected] > http://www.omnigroup.com/mailman/listinfo/macosx-admin _______________________________________________ MacOSX-admin mailing list [email protected] http://www.omnigroup.com/mailman/listinfo/macosx-admin
