User Subdomain Issues
About how to implement the separation of users in their subdomains here already written. The pros and cons of the idea of bringing out the login to the subdomain were not only affected. So.
2. Each user has “everything starts anew”, i.e. here % username% .domain.com / blog has a blog, and then % username% .domain.com / mail has a mail.
2. All links must be placed absolutely ( % username% .domain.com / and domain.com/ - different addresses, just href = "/" you will not write).
3. Third-party scripts will overwhelm you with cookies (see, for example, how many Habrovsky cookies you have from Google analytics).
4. If some private zone is located on a subdomain ( % username% .domain.com / settings ), then in order to explain something to a newbie, then you simply will not give your link (it has come across many times).
5. There will not be a good hierarchy if the resource owner needs at least one subdomain for its own purposes (www, mail etc).
6. How to see a list of all users? With the domain.com/users/%username% structure , the solution is obvious - domain.com/users/ , and with % username% .domain.com / where to look for such a page?
7. In the domain name, the list of prohibited characters is much more than in path. For example, if the login vasya_pupkin can be safely written in the path as the directory name, then when moving to the subdomain you will have to change to vasya-pupkin .
On large well-known resources (not w20), solutions without subdomains (http://users.nnm.ru/%username%, free-lance.ru/users/%username% ) have been used successfully for a long time, which avoids almost all minuses without losing the benefits. So where did this problematic idea come from to put the username into a subdomain?
pros
1. So beautiful, there is a logical division into the area of each user.2. Each user has “everything starts anew”, i.e. here % username% .domain.com / blog has a blog, and then % username% .domain.com / mail has a mail.
Minuses
1. All addresses on the site must be absolutely registered (for pictures, scripts).2. All links must be placed absolutely ( % username% .domain.com / and domain.com/ - different addresses, just href = "/" you will not write).
3. Third-party scripts will overwhelm you with cookies (see, for example, how many Habrovsky cookies you have from Google analytics).
4. If some private zone is located on a subdomain ( % username% .domain.com / settings ), then in order to explain something to a newbie, then you simply will not give your link (it has come across many times).
5. There will not be a good hierarchy if the resource owner needs at least one subdomain for its own purposes (www, mail etc).
6. How to see a list of all users? With the domain.com/users/%username% structure , the solution is obvious - domain.com/users/ , and with % username% .domain.com / where to look for such a page?
7. In the domain name, the list of prohibited characters is much more than in path. For example, if the login vasya_pupkin can be safely written in the path as the directory name, then when moving to the subdomain you will have to change to vasya-pupkin .
On large well-known resources (not w20), solutions without subdomains (http://users.nnm.ru/%username%, free-lance.ru/users/%username% ) have been used successfully for a long time, which avoids almost all minuses without losing the benefits. So where did this problematic idea come from to put the username into a subdomain?
')
Source: https://habr.com/ru/post/26813/
All Articles