From: Robert Robinson <
rnlro...@gmail.com>
>What does everybody else do? Do you have defined practices around new
>subdomains?
>
>Should I stick to my guns, are the more arguments I'm missing, or should
>I just relax and do it?
Robert,
it is true that there are a small percentage of people who will get it
wrong, no matter which way you prefer it. I think it's best to be kind and
not show them an error, so I prefer is to capture both as your admin is
suggesting.
We add the www version into the DNS and rewrite/strip it out it at the
server level. As long as the rewrites are handled correctly, nobody ever
sees the www url in their browser, no issues. Certainly haven't noticed
any SEO problems.
...and, just following on from that, there are jolly good reasons for
*not* having the www when the page finally loads in a browser...
We use a 'wild card' certificate to provide SSL to all subdomains.
However,
www.something.unimelb.edu.au is a sub-subdomain, and is not
covered by that certificate, which can cause insecure content errors on
login pages etc.
So, unless your admin is offering to pay for all those separate
certificates - go the rewrite!
Cheers,
Andrew
--
Andrew Harris, Interface Designer
Online Services, Information Technology Services
Level 2, 258 Queensberry Street, University of Melbourne, 3010, VIC
Telephone
+61 3 8344 2865 : Email
aha...@unimelb.edu.au
This email and any attachments may contain personal information or
information that is otherwise confidential or the subject of copyright.
Any use, disclosure or copying of any part of it is prohibited. The
University does not warrant that this email or any attachments are free
from viruses or defects. Please check any attachments for viruses and
defects before opening them. If this email is received in error please
delete it and notify us by return email.