next-i18nnext with domain routing problem
Unanswered
Russian Blue posted this in #help-forum
Russian BlueOP
problem : assets from public dir are only available on domain with default lang
as my default lang is "en" thats only domain that eg. /robots.txt can be shown
i tried doing middleware with matcher to exclude every non translatable paths but still not working
any clue what can be reason of such weird bug ?
middleware so far looks like this
versions :
"next": "^13.4.10",
"next-i18next": "^13.2.2",
as my default lang is "en" thats only domain that eg. /robots.txt can be shown
i tried doing middleware with matcher to exclude every non translatable paths but still not working
any clue what can be reason of such weird bug ?
middleware so far looks like this
matcher: [
'/((?!_next).*)',
'/((?!images).*)',
'/((?!video).*)',
'/((?!documents).*)',
'/((?!img).*)',
'/((?!locales).*)',
'/((?!static).*)',
'/((?!robots.txt).*)'
]versions :
"next": "^13.4.10",
"next-i18next": "^13.2.2",
2 Replies
Russian BlueOP
i made workaround over nginx with
i leave it open maybe someone will find proper solution
location ~ \.(png|jpg|mp4|html|txt|webm|ogv|css|json|xml|ico|pdf) {
root /var/www/html/[...]/current/public;
}i leave it open maybe someone will find proper solution
Russian BlueOP
upgrading next to "next": "13.4.12", fixed issue closing