Hello Sebastian, thank you for your support.
I don't see DNN work in such a way.
I configured N alias, all primary for the same domain:
www.mysite.com language "empty", primary
www.mysite.com/en-us language en-us, primary
www.mysite.com/fr-fr language fr-fr, primary
www.mysite.com/es-es language es-es, primary
The domain is the same.
I also configured the pages in order to have the same page name in all the languages, so I have
http://www.mysite.com/en-us/mypage (tabid:700)
http://www.mysite.com/fr-fr/mypage (tabid:701)
http://www.mysite.com/es-es/mypage (tabid:702)
And these pages work well.
What I see is that if I call www.mysite.com/mypage "without the culture code" the browser detection doesn't work, and is loaded the latest localized page (by tabid order), in this example www.mysite.com/es-es/mypage
I think that the problem may reside in the same page title that I configured on the localized pages.
When you localize a page DNN offers different page title for the localized pages, i.e. mypage (FR) and mypage (ES).
I configured the same page title in order to have the url ending in the same way in all the languages. But it seems that this configuration may interfere with the browser detection feature. Am I missing something ?