---- Christoph <[EMAIL PROTECTED]> wrote: > > Don't do that. > > Some sites may or may not use www. for whatever reason... > > Usually screwed-up A-name records by incompetent sysadmins, but there > > it is... > > Really? So > > games.yahoo.com > blogreport.salon.com > mirror1.downloads.com > > are examples of screwed up records by incompetent sysadmins? > > thnx, > Chris
No, these are examples of ones set up specifically for specific purposes. Just like http://lonewolf.homelinux.net/ can actually resolve correctly when www is placed at the front due to my settings. However a site like http://nc4h.org actually NEEDS to have the www in the front because the sysadmins haven't corrected a known issue for 3 years now. But the point is, there are a number of sites which don't have a www in the front for a specific and valid reason, and other times where the sysadmins are just morons. Making any site re-direct to www as a cause is just overhead not needed, either your site works correctly or you talk with your sysadmin about getting the records corrected and the server correct to respond to requests in any flavor for your site's specific needs. And if you do it right, you use the server to mod_rewrite the url and you are golden. Wolf -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
