-
-
Notifications
You must be signed in to change notification settings - Fork 2
Description
Hi,
our website respond at : https://domain.com/fr-fr/
( it's the default store_view from the default store_group fr
in the website named as main_domain
(it's not the default website of global Magento instance) and https://domain.com/fr-en/
(another store_view from the default store_group fr
in our website named as main_domain ) but I wonder why the URL https://domain.com/fr-nl/
return 200
and https://domain.com/fr-00/
too (and any url with 1-5 characters in the path return 200
)
https://domain.com/1
return200
(❌ unexpected)https://domain.com/12
return200
(❌ unexpected)https://domain.com/123
return200
(❌ unexpected)https://domain.com/1234
return200
(❌ unexpected)https://domain.com/12345
return200
(❌ unexpected)https://domain.com/123456
return404
(✅ expected)https://domain.com/-_,!~
return200
too (❌ unexpected)
When return 200
, it's the default store view for default store_group than is loaded (path: fr-fr
) (✅ expected)
(I have 41^5 (115856201) stores now #joke (I'm seriously thinking about asking my boss for a raise. 🤔) )
There is a configuration in adminhtml I have missed ?
Our Fastly / Varnish configurations catch only the tld of the domain and in my opinion, the issue would not be located at this level
EDIT
The others website (respond for default-domain.com
(default website) or another-domain.com
on the same Magento instance is impacted too).
The path for default store_view in default store_group in default-domain.com
contain actually 9 chars
https://default-domain.com/1
return200
(❌ unexpected)https://default-domain.com/12345
return200
(❌ unexpected)https://default-domain.com/1234567890
return200
(❌ unexpected)https://default-domain.com/12345678901
return404
(✅ expected)
The path for default store_view in default store_group in another-domain.com
contain actually 5 chars
https://another-domain.com/12345
return200
(❌ unexpected)https://another-domain.com/123456
return404
(✅ expected)