I don't know how we got to Version 3.0 without proper "www" subdomain handling, but it will be a staple starting in 3.1. You can try to break it at Sueetie.com by loading up a www.sueetie.com page. Any page, any application, it won't happen. This is important for a couple of reasons. First, SEO consistency. I've used a global.asax 301 redirect at sueetie.com, but I should have done it right the first time. The global.asax redirect didn't play well with the Sueetie UrlRedirect HttpModule and displayed the physical url of /themes/THEME/pages/whatever.aspx. I didn't type in a "www" in six years, so it wasn't something I thought to test. The second reason for "www" handling is because some Sueetie sites have been seeing some WCF services issues with "www" domain urls when not explicitly configured that way in the web.config.
Not much sexy about www subdomain handling. Just another lollipop in the wall. Here's where you'll set the www handling on the Sueetie General Settings admin page.
