When should one use a 'www' subdomain? -


While browsing through the Internet for the last few years, I see more and more pages to get rid of 'www' I am subdomain.

Is there no good reason to use the 'www' subdomain to use?

There are many good reasons to include, the best of which is here:

Due to the Dot rule with cookies, if you do not have 'www'. You can not set up La * .example.com to two dot cookie or cross-subdomain cookies. There are two relevant effects

First it means that any users who are giving you the cookie will return those cookies back with the requests that match the domain. So even if you have a subdomain, the images.example.com, example.com cookie will always be sent with the requests of that domain. It creates overhead which will not exist if you have made www.example.com the official name. Of course you can use a CDN, but it depends on your resources.

In addition, you do not have the ability to set a cross-subdomain cookie, it seems obvious, but this means that authenticated users are allowed to move between their subdomains more than the technical challenge.

Ask yourself some questions, do I set a cookie? Do I care about potentially unnecessary bandwidth expenditures? Will the certified users cross the subdomain? If you are really worried about the inconvenience to the user, then you can always configure your server to take care of your server www / no www.

See and


Comments