URL Culture & Hostnames - One Level Paths should be avoided?
Under Umbraco's Culture and Hostnames there is the following warning posted:One-level paths in domains are supported, eg. "example.com/en". However, they should be avoided. Better use the culture setting above.
Can someone please advise why they should be avoided? We would like to use www.url.com/folder to prevent caching issues however if it will cause more issues to use one level paths, then can that be explained and what an alternative might be?
Honestly, I would also go for the One-level paths in domains. I dont know why they advise to go against it. For caching and user login authorization it is much easier to handle example.com/en, example.com/fr.
On my own ASP.NET web application im using this. It is not Umbraco tho.
Hmmm. I've always used the example.com/en, example.com/ one level domains for multilingual sites and not had any issue. I use this in conjunction with the culture settings. I'm sure this warning never used to appear and I'm curious to why it suddenly has?
URL Culture & Hostnames - One Level Paths should be avoided?
Under Umbraco's Culture and Hostnames there is the following warning posted: One-level paths in domains are supported, eg. "example.com/en". However, they should be avoided. Better use the culture setting above.
Can someone please advise why they should be avoided? We would like to use www.url.com/folder to prevent caching issues however if it will cause more issues to use one level paths, then can that be explained and what an alternative might be?
Please see screenshot with blue highlighted text:
Thank you!
Honestly, I would also go for the One-level paths in domains. I dont know why they advise to go against it. For caching and user login authorization it is much easier to handle example.com/en, example.com/fr.
On my own ASP.NET web application im using this. It is not Umbraco tho.
An old explanation of umbraco culture methods, but still seems viable, can be found here: culture and hostnames difference
Hmmm. I've always used the
example.com/en, example.com/one level domains for multilingual sites and not had any issue. I use this in conjunction with the culture settings. I'm sure this warning never used to appear and I'm curious to why it suddenly has?is working on a reply...